Triple
T35701569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transcontinental Air Transport |
E1031598
|
entity |
| Predicate | dayTravelSegment |
P60863
|
FINISHED |
| Object | by air |
—
|
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: by air | Statement: [Transcontinental Air Transport, dayTravelSegment, by air]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dayTravelSegment Context triple: [Transcontinental Air Transport, dayTravelSegment, by air]
-
A.
connectsTravelBetween
Indicates a relationship where something (such as a route, service, or mode of transport) enables or provides travel between two locations.
-
B.
transportSegment
chosen
Indicates a distinct portion of a larger journey or route during which something or someone is transported from one point to another.
-
C.
destinationOfFlight
Indicates the location or place to which a given flight is traveling or scheduled to arrive.
-
D.
crewTransportSegment
Indicates a segment of a journey during which crew members are transported from one location to another.
-
E.
passengerFlight
Indicates a relationship where a flight is specifically operated to transport passengers rather than cargo or other purposes.
- 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_69f76e0d393c8190b6303c64408736db |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.