Triple
T18727844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York–London |
E457952
|
entity |
| Predicate | typicalNonstopDurationHours |
P1526
|
FINISHED |
| Object | 6–8 |
—
|
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: 6–8 | Statement: [New York–London, typicalNonstopDurationHours, 6–8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalNonstopDurationHours Context triple: [New York–London, typicalNonstopDurationHours, 6–8]
-
A.
flightDuration
chosen
Indicates the length of time that a specific flight takes from departure to arrival.
-
B.
isNonStop
Indicates that a service, trip, or process occurs from start to finish without any intermediate stops or interruptions.
-
C.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
D.
voyageDuration
Indicates the length of time that a voyage or journey lasts from its start to its end.
-
E.
isNonstopPossible
Indicates that it is possible to perform or complete the referenced trip, route, or process without any intermediate stops or interruptions.
- 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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56d74bd9881908cd314e68327c402 |
completed | April 20, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69e48d03766c8190a43f7681842f4f8d |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:50 a.m.