Triple
T37549577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Airlines |
E933554
|
entity |
| Predicate | servedDestinationRegion |
P104635
|
FINISHED |
| Object | United States |
—
|
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: United States | Statement: [Western Airlines, servedDestinationRegion, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedDestinationRegion Context triple: [Western Airlines, servedDestinationRegion, United States]
-
A.
servedDestination
Indicates that a service or action is directed toward, or provided to, a particular destination.
-
B.
hasDestinationRegion
Indicates that something is directed, sent, or intended to arrive at a particular geographic or logical region as its destination.
-
C.
issuerRegionServed
Indicates the geographic region or area that the issuer provides services to or operates within.
-
D.
destinationCountryServed
chosen
Indicates that a given entity (such as a service, route, or provider) serves or operates to a specified destination country.
-
E.
servedDomesticDestination
Indicates that a transportation service (such as an airline or train operator) provided service to a destination located within the same country.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a007338002081908cb6340d65ff86d5 |
completed | May 10, 2026, 11:59 a.m. |
| PD | Predicate disambiguation | batch_6a0072a137ac8190a7debeb28e738e03 |
completed | May 10, 2026, 11:57 a.m. |
Created at: May 3, 2026, 4:17 p.m.