Triple
T36740184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Athletics Indoor Championships |
E907587
|
entity |
| Predicate | eventsIncluded |
P58905
|
FINISHED |
| Object | sprints |
—
|
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: sprints | Statement: [European Athletics Indoor Championships, eventsIncluded, sprints]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventsIncluded Context triple: [European Athletics Indoor Championships, eventsIncluded, sprints]
-
A.
includesEvents
chosen
Indicates that one entity contains or encompasses one or more events as part of its scope or composition.
-
B.
multiEventsIncluded
Indicates that multiple distinct events are collectively contained within, or form part of, a larger event set or grouping.
-
C.
eventSchedule
Indicates that an event is associated with a specific planned time, date, or sequence within a schedule.
-
D.
individualEvents
Indicates that the subject is associated with one or more distinct, separately identifiable events rather than a single aggregated or continuous occurrence.
-
E.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
- 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_69f76e75aa6881909b844d00a3888ee5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:12 p.m.