Triple
T31712607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSA Airlines |
E809366
|
entity |
| Predicate | hasCrewBase |
P181773
|
FINISHED |
| Object | Charlotte Douglas International Airport |
—
|
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: Charlotte Douglas International Airport | Statement: [PSA Airlines, hasCrewBase, Charlotte Douglas International Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCrewBase Context triple: [PSA Airlines, hasCrewBase, Charlotte Douglas International Airport]
-
A.
hasCrewQuarters
Indicates that one entity provides or contains designated living or sleeping quarters for the crew associated with it.
-
B.
hasExtendedCrew
Indicates that an entity is associated with an additional or supplementary group of crew members beyond its primary crew.
-
C.
hasCrewedComponent
Indicates that an entity includes or is associated with a component that is operated or occupied by a crew.
-
D.
hasCrewCapacity
Indicates that an entity is capable of accommodating a specified number of crew members.
-
E.
hasCrewFeature
Indicates that a crew possesses or is characterized by a particular feature, attribute, or capability.
- F. None of above. chosen
Provenance (4 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_69f348df4e048190a4a5a9932ada78d6 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7824dc3f0819092a5102895b4a478 |
completed | May 3, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f7817c79e081908e685c48165e086b |
completed | May 3, 2026, 5:10 p.m. |
Created at: April 30, 2026, 11:16 p.m.