Triple
T675766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1896 Summer Olympics |
E13073
|
entity |
| Predicate | marathonDistanceKilometres |
P7750
|
FINISHED |
| Object | about 40 |
—
|
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: about 40 | Statement: [1896 Summer Olympics, marathonDistanceKilometres, about 40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marathonDistanceKilometres Context triple: [1896 Summer Olympics, marathonDistanceKilometres, about 40]
-
A.
navigableLengthApproxKm
Indicates the approximate distance, measured in kilometers, over which something (typically a waterway) can be navigated.
-
B.
distance
chosen
Indicates the spatial separation or length between two points, objects, or locations.
-
C.
runwayLength
Indicates the length of a runway associated with an airport or airfield.
-
D.
distanceTraveled
Indicates the total length of the path an entity has moved over a period of time or between two points.
-
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_69a4933d3bf88190972041cd8cf143b9 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a0266e7c8190a94c4b4b761c59f4 |
completed | March 1, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69a49d1bbd0c81909cfbec30bd17bde7 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.