Triple
T28807064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Islamabad–London |
E727406
|
entity |
| Predicate | approximateNonstopDuration |
P109944
|
FINISHED |
| Object | 8 hours |
—
|
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: 8 hours | Statement: [Islamabad–London, approximateNonstopDuration, 8 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateNonstopDuration Context triple: [Islamabad–London, approximateNonstopDuration, 8 hours]
-
A.
hasApproximateDuration
Indicates that one entity has a duration that is estimated or not exact, typically expressed as an approximate length of time.
-
B.
lengthInMinutes
Indicates the duration of something expressed as a number of minutes.
-
C.
intendedDuration
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
-
D.
commonDuration
Indicates that two or more events, actions, or states share the same length of time.
-
E.
approximateTripDuration
chosen
Indicates the estimated length of time required to complete a trip between specified locations or points in a journey.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: April 28, 2026, 6:29 a.m.