Triple
T1115917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1908 Summer Olympics |
E11099
|
entity |
| Predicate | marathonDistance |
P20127
|
FINISHED |
| Object | 26 miles 385 yards |
—
|
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: 26 miles 385 yards | Statement: [1908 Summer Olympics, marathonDistance, 26 miles 385 yards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marathonDistance Context triple: [1908 Summer Olympics, marathonDistance, 26 miles 385 yards]
-
A.
majorRaceDistance
chosen
Indicates the standard or primary distance over which a major race or competition is contested.
-
B.
marathonWinner
Indicates that one entity is the competitor who finished first and won a specified marathon event.
-
C.
range_km
Indicates the maximum distance, measured in kilometers, over which something can operate, travel, or be effective.
-
D.
distance
Indicates the spatial separation or length between two points, objects, or locations.
-
E.
hourRecordDistance
Indicates that one entity holds or represents the record for the greatest distance covered within a one-hour time period relative to another entity or context.
- 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_69a493252a648190ac48f8742474a5e8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bbd92a8c8190a16e55f3f739010f |
completed | March 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69a4bb42990c819080db96478fd4977e |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:43 p.m.