Triple
T24262000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dodge City Regional Airport |
E604729
|
entity |
| Predicate | hasScheduledServiceBy |
P6787
|
FINISHED |
| Object | United Express |
—
|
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 Express | Statement: [Dodge City Regional Airport, hasScheduledServiceBy, United Express]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScheduledServiceBy Context triple: [Dodge City Regional Airport, hasScheduledServiceBy, United Express]
-
A.
hasServiceTo
chosen
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
B.
scheduledServiceType
Indicates the type or category of service that has been scheduled between entities (e.g., maintenance, appointment, or delivery).
-
C.
hasScheduleType
Indicates that an entity is associated with a particular kind or category of schedule (e.g., recurring, one-time, or specific scheduling pattern).
-
D.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
E.
hasThroughServiceWith
Indicates that two transportation services are operationally linked so that a passenger or shipment can continue from one to the other without a separate booking or major interruption.
- 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_69e29544c29c8190b023606eafe5d36a |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28c6727388190862e3ce09c372c70 |
completed | April 29, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:06 a.m.