Triple
T20676714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asian Youth Games |
E508176
|
entity |
| Predicate | firstEditionStartDate |
P141002
|
FINISHED |
| Object | 2009-06-29 |
—
|
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: 2009-06-29 | Statement: [Asian Youth Games, firstEditionStartDate, 2009-06-29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstEditionStartDate Context triple: [Asian Youth Games, firstEditionStartDate, 2009-06-29]
-
A.
firstEditionEndYear
Indicates the year in which the first edition of something (such as a work, event, or series) concluded or ceased to be current.
-
B.
firstTypicalEditionYear
Indicates the year in which the first typical or standard edition of a work was published or officially issued.
-
C.
firstEditionPublicationYear
Indicates the year in which an entity’s first edition was originally published.
-
D.
firstCollectedEditionYear
Indicates the year in which the first collected edition of a work was published or made available.
-
E.
inceptionOfEdition
Indicates the event or point in time at which a particular edition of a work is first created, initiated, or brought into existence.
- 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_69e0b4c1164881909a3bf1e3ddb2bc32 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6bea24f288190928f828e5f567257 |
completed | April 21, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69e5c03caee881908be4dd25796a03d5 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 11:44 a.m.