Triple
T28361783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YUM |
E718379
|
entity |
| Predicate | civilianTerminalOperator |
P86510
|
FINISHED |
| Object | Yuma County Airport Authority |
—
|
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: Yuma County Airport Authority | Statement: [YUM, civilianTerminalOperator, Yuma County Airport Authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: civilianTerminalOperator Context triple: [YUM, civilianTerminalOperator, Yuma County Airport Authority]
-
A.
terminusAAirport
Indicates that an airport serves as the terminal (end) point for a specified air route or service.
-
B.
hasPassengerTerminalSector
Indicates that a passenger terminal is divided into or associated with a specific sector or subsection within it.
-
C.
airportRole
Indicates that an entity serves a specific functional role or capacity within the context of an airport.
-
D.
operatesTerminalsIn
chosen
Indicates that an entity manages or runs the operations of one or more terminals at a given location or facility.
-
E.
civilOperator
Indicates that an entity performs or is responsible for operating a civil (non-military) system, service, or infrastructure.
- 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_69eff6ed5af48190be4e0adf298223e0 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 12:52 a.m.