Triple
T6532869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2017 IAAF World Championships in Athletics |
E152273
|
entity |
| Predicate | mainSurface |
P40183
|
FINISHED |
| Object | synthetic track |
—
|
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: synthetic track | Statement: [2017 IAAF World Championships in Athletics, mainSurface, synthetic track]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainSurface Context triple: [2017 IAAF World Championships in Athletics, mainSurface, synthetic track]
-
A.
secondarySurface
Indicates a relationship where one surface functions as a secondary or subordinate surface in relation to a primary or main surface.
-
B.
formerSurface
Indicates that one entity previously served as the surface or outer layer of another entity, but no longer does so.
-
C.
usesSurface
Indicates that one entity employs or interacts with another entity as a surface or platform for its action or function.
-
D.
hasPrimarySurface
chosen
Indicates that one entity serves as the main or principal surface associated with another entity.
-
E.
mainRite
Indicates that one ritual, ceremony, or rite is the primary or central rite associated with a given context, entity, or 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_69c688048ec8819093a47f7d332e12ec |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6adbe168881908ffefc4962e2893d |
completed | March 27, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69c68abd9c7c819099e4fe8097cd1b28 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:46 p.m.