Triple
T8380928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4 × 400 metres relay at the 1924 Summer Olympics |
E197684
|
entity |
| Predicate | isTrackEvent |
P81754
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [4 × 400 metres relay at the 1924 Summer Olympics, isTrackEvent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTrackEvent Context triple: [4 × 400 metres relay at the 1924 Summer Olympics, isTrackEvent, true]
-
A.
hasTrack
Indicates that one entity possesses, includes, or is associated with a specific track (such as a path, course, or recorded item).
-
B.
isTrackedBy
Indicates that an entity’s state, behavior, or changes are being monitored, recorded, or followed by another entity.
-
C.
isLinkedToEvent
Indicates that an entity has an association or connection with a specific event.
-
D.
usesTrackage
Indicates that one transportation operator or service runs its vehicles over railway or transit tracks that are owned or controlled by another entity.
-
E.
trackOn
Indicates that one entity is physically positioned or moving along the surface or path of another, like a vehicle on a track or rails.
- 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_69ca82f64c188190af4e1608036b865d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80c57080819097eef2b7e46eaaee |
completed | March 31, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69cb70cfe82881909fe374ba52649e84 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76da264881909483b835e1db06da |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 6:02 p.m.