Triple
T22664960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Youth Championships |
E559759
|
entity |
| Predicate | hasTypicalEvents |
P7008
|
FINISHED |
| Object | track and field events |
—
|
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: track and field events | Statement: [World Youth Championships, hasTypicalEvents, track and field events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalEvents Context triple: [World Youth Championships, hasTypicalEvents, track and field events]
-
A.
hasOccasionalEvent
Indicates that an event or activity occurs irregularly or infrequently in relation to a given entity or context.
-
B.
typicalEvent
chosen
Indicates that the associated event is a common, characteristic, or prototypical occurrence for the given entity or situation.
-
C.
hadEvent
Indicates that an entity experienced, hosted, or was associated with a specific event at some point in time.
-
D.
typicalEventDay
Indicates the day on which an event is normally or most commonly held or occurs.
-
E.
includesEvents
Indicates that one entity contains or encompasses one or more events as part of its scope or composition.
- F. None of above.
Provenance (3 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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1781b3dbc8190a312843cf8c1bfc6 |
completed | April 29, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:08 p.m.