Triple
T11642587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seoul–London |
E276692
|
entity |
| Predicate | typicalNonstopDistanceMi |
P1525
|
FINISHED |
| Object | approximately 5460 |
—
|
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 5460 | Statement: [Seoul–London, typicalNonstopDistanceMi, approximately 5460]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalNonstopDistanceMi Context triple: [Seoul–London, typicalNonstopDistanceMi, approximately 5460]
-
A.
firstFlightDistance
Indicates the distance covered during an entity’s first recorded flight.
-
B.
isNonStop
Indicates that a service, trip, or process occurs from start to finish without any intermediate stops or interruptions.
-
C.
maximumRangeNauticalMiles
Indicates the greatest distance, measured in nautical miles, that something can travel or operate under specified conditions.
-
D.
flightDistance
chosen
Indicates the measured distance covered by a flight between its origin and destination.
-
E.
lengthInKm
Indicates that one entity specifies the length or distance of another entity measured in kilometers.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a260ab488190ab1c00d9850f3096 |
completed | April 10, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.