Triple
T14545822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sydney–Melbourne air route |
E341288
|
entity |
| Predicate | typicalFlightTime |
P1526
|
FINISHED |
| Object | about 1 hour 25 minutes |
—
|
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 1 hour 25 minutes | Statement: [Sydney–Melbourne air route, typicalFlightTime, about 1 hour 25 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFlightTime Context triple: [Sydney–Melbourne air route, typicalFlightTime, about 1 hour 25 minutes]
-
A.
flightDuration
chosen
Indicates the length of time that a specific flight takes from departure to arrival.
-
B.
flightHours
Indicates the number of hours an entity has spent in flight or operating in the air.
-
C.
flightPeriod
Indicates the time span during which a flight occurs or is scheduled to operate.
-
D.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
E.
timeAfterTakeoff
Indicates that a specified time point occurs after the moment of takeoff in a flight or launch sequence.
- 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_69d822db9c8481908213ceb39585f792 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb1bfc2b48190adb0897682c26a9a |
completed | April 14, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69de5c546c7081909e27d504ec360c5c |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:22 a.m.