Triple
T24650229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing 247 |
E610227
|
entity |
| Predicate | airlineServiceStartRoute |
P66394
|
FINISHED |
| Object | Chicago–Newark |
—
|
NE NERFINISHED |
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: Chicago–Newark | Statement: [Boeing 247, airlineServiceStartRoute, Chicago–Newark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airlineServiceStartRoute Context triple: [Boeing 247, airlineServiceStartRoute, Chicago–Newark]
-
A.
airlineServiceVia
Indicates that an airline service operates between two locations with a specified intermediate stop or transit point.
-
B.
airlineService
Indicates that an airline operates transportation services (such as flights) between specified locations or for specified routes.
-
C.
airlineServiceEntry
chosen
Indicates the initiation or presence of an airline’s operational service on a particular route, schedule, or location.
-
D.
airlineContext
Indicates a relationship, situation, or action that specifically occurs within or is constrained by an airline-related context (such as flights, carriers, or air travel operations).
-
E.
airlineHubRoute
Indicates a route that connects an airline’s designated hub airport with another airport in its network.
- 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_69e2c4d350a481909170482bc2ce6af9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 2:33 a.m.