Triple
T19529353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dangun myth |
E488617
|
entity |
| Predicate | bearUndergoesTrialWith |
P136656
|
FINISHED |
| Object | garlic |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: garlic | Statement: [Dangun myth, bearUndergoesTrialWith, garlic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearUndergoesTrialWith Context triple: [Dangun myth, bearUndergoesTrialWith, garlic]
-
A.
undergoing
Indicates that an entity is currently experiencing, being subjected to, or in the process of a particular action, change, or treatment.
-
B.
onTrialFor
Indicates that a person is currently being legally prosecuted or judged in court for a specific alleged offense or charge.
-
C.
wasTriedBy
Indicates that a legal case or charge involving an entity was examined and judged in a trial conducted by another entity (such as a court or judge).
-
D.
canBeBorneBy
Indicates that one entity is capable of being carried, supported, or transported by another entity.
-
E.
triedBy
Indicates that an entity has made an attempt to perform an action on, or in relation to, another entity.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6363dfd6c8190aaa0b374184965bb |
completed | April 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
| PDg | Predicate description generation | batch_69e51a23300c8190988552491d9783d7 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 1:41 p.m.