Triple
T28384884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | men's 100 metres at the 1924 Summer Olympics |
E718992
|
entity |
| Predicate | laneStartType |
P30569
|
FINISHED |
| Object | standing start |
—
|
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: standing start | Statement: [men's 100 metres at the 1924 Summer Olympics, laneStartType, standing start]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laneStartType Context triple: [men's 100 metres at the 1924 Summer Olympics, laneStartType, standing start]
-
A.
raceStartType
chosen
Indicates the manner or format in which a race is initiated (e.g., type or method of starting the race).
-
B.
laneStructure
Indicates the structural organization and configuration of lanes within a roadway or traffic facility.
-
C.
laneSurface
Indicates the type or condition of the surface that makes up a lane used for travel or traffic.
-
D.
starterType
Indicates the classification or category of a starter (e.g., initial component, opening item, or first phase) associated with an entity or process.
-
E.
laneRequirement
Indicates that a specified number or type of lanes is required for a particular movement, maneuver, or use on a roadway.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64cba41748190a0cf070481fc7fd8 |
completed | May 2, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 1:09 a.m.