Triple
T15068891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concourse D |
E379824
|
entity |
| Predicate | servedAirlinesRole |
P9478
|
FINISHED |
| Object | regional jet hub |
—
|
LITERAL FINISHED |
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: regional jet hub | Statement: [Concourse D, servedAirlinesRole, regional jet hub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedAirlinesRole Context triple: [Concourse D, servedAirlinesRole, regional jet hub]
-
A.
usedByAirlineRole
Indicates that something (such as a resource, system, or process) is utilized by a specific role or position within an airline organization.
-
B.
servesAirline
Indicates that a transportation facility or location provides service for, or is regularly used by, a specified airline.
-
C.
servesAirlineType
chosen
Indicates that a service provider (such as an airport, terminal, or facility) accommodates or operates flights for a specified type or category of airline.
-
D.
airlineAllianceRole
Indicates the specific role or function an airline holds within an airline alliance.
-
E.
servesAirlinesFrom
Indicates that a location or facility provides service or operations for flights belonging to specific airlines originating from that place.
- 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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dedeebc7e48190a86b4f0afe8844bb |
completed | April 15, 2026, 12:42 a.m. |
| PD | Predicate disambiguation | batch_69deb95a182081908fffc4402b02a394 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:02 a.m.