Triple
T8380914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4 × 400 metres relay at the 1924 Summer Olympics |
E197684
|
entity |
| Predicate | legOrder |
P81751
|
FINISHED |
| Object | fixed running order submitted before race |
—
|
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: fixed running order submitted before race | Statement: [4 × 400 metres relay at the 1924 Summer Olympics, legOrder, fixed running order submitted before race]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legOrder Context triple: [4 × 400 metres relay at the 1924 Summer Olympics, legOrder, fixed running order submitted before race]
-
A.
hasHindLegsOf
Indicates that one entity possesses or is characterized by the hind legs belonging to or derived from another entity.
-
B.
numberOfLegs
Indicates the quantity of legs that an entity possesses.
-
C.
legs
Indicates that an entity possesses legs, specifying the presence or number of leg-like appendages associated with it.
-
D.
legFeathering
Indicates that an entity possesses feathers growing on or covering its legs.
-
E.
legOrientation
Indicates the relative positioning or directional alignment of an entity’s leg(s) with respect to a reference frame or another object.
- 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.