Triple
T5482031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 20th Century Limited |
E123487
|
entity |
| Predicate | routeDistance |
P7750
|
FINISHED |
| Object | approximately 960 miles |
—
|
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: approximately 960 miles | Statement: [20th Century Limited, routeDistance, approximately 960 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeDistance Context triple: [20th Century Limited, routeDistance, approximately 960 miles]
-
A.
flightDistance
Indicates the measured distance covered by a flight between its origin and destination.
-
B.
trailDistanceApprox
Indicates that the distance along a trail between two locations is approximately a specified value, allowing for some margin of error.
-
C.
distance
chosen
Indicates the spatial separation or length between two points, objects, or locations.
-
D.
distanceCharacteristic
Indicates a relationship where an entity is described or constrained by some property or measure of distance (e.g., range, spacing, or separation).
-
E.
distanceTraveled
Indicates the total length of the path an entity has moved over a period of time or between two points.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd93e5d0f08190a6cc9fc408b7c5bb |
completed | March 20, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69bd91a73b148190a865243536a4fe76 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.