Triple
T31759945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Midwest |
E810652
|
entity |
| Predicate | servedAsFeederFor |
P67487
|
FINISHED |
| Object | US Airways |
—
|
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: US Airways | Statement: [Air Midwest, servedAsFeederFor, US Airways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedAsFeederFor Context triple: [Air Midwest, servedAsFeederFor, US Airways]
-
A.
hasFeederRelationshipTo
chosen
Indicates that one entity serves as a source of nourishment, resources, or input that sustains, supports, or feeds another entity.
-
B.
mainFeederOf
Indicates that one entity serves as the primary source or supplier of resources, energy, or input to another entity.
-
C.
isFedBy
Indicates that one entity receives nourishment, food, or sustenance from another entity.
-
D.
hasFeederUnion
Indicates that an entity is associated with or connected to a feeder union, typically one that supplies members, resources, or support to it.
-
E.
feederSystem
Indicates a system or mechanism that supplies or feeds resources, materials, or inputs into another process, component, or structure.
- 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_69f348e340d48190b780fae618c51464 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fee691952c8190822da83e46311d1d |
completed | May 9, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69fee62f285c8190a625562a9b80526e |
completed | May 9, 2026, 7:45 a.m. |
Created at: April 30, 2026, 11:30 p.m.