Triple
T9241598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manila–Tokyo |
E222071
|
entity |
| Predicate | typicalFlightDuration |
P1526
|
FINISHED |
| Object | 4 to 5 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: 4 to 5 hours | Statement: [Manila–Tokyo, typicalFlightDuration, 4 to 5 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFlightDuration Context triple: [Manila–Tokyo, typicalFlightDuration, 4 to 5 hours]
-
A.
flightDuration
chosen
Indicates the length of time that a specific flight takes from departure to arrival.
-
B.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
C.
flightPeriod
Indicates the time span during which a flight occurs or is scheduled to operate.
-
D.
typicalDestinationAirportIATA
Indicates the IATA airport code that is typically the destination in this kind of trip or route.
-
E.
voyageDuration
Indicates the length of time that a voyage or journey lasts from its start to its end.
- 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_69ca83ee26cc81909ac624e190597d6d |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cd03ea9d90819096f9ca5321dffd56 |
completed | April 1, 2026, 11:39 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4765648190aa9445c4a22dc471 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:30 p.m.