Triple
T25866518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concourse E |
E651630
|
entity |
| Predicate | hasPowerOutlets |
P56287
|
FINISHED |
| Object | passenger seating areas |
—
|
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: passenger seating areas | Statement: [Concourse E, hasPowerOutlets, passenger seating areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPowerOutlets Context triple: [Concourse E, hasPowerOutlets, passenger seating areas]
-
A.
offersOnboardPowerOutlets
chosen
Indicates that the subject provides power outlets available for use during the onboard experience.
-
B.
powerRival
Indicates a relationship where two entities compete or conflict over power, influence, or control.
-
C.
hasPowerRegulator
Indicates that an entity is equipped with or connected to a power regulator component that controls or stabilizes its electrical power.
-
D.
hasPowerTerminal
Indicates that an entity is equipped with or connected to a power terminal through which electrical power can be supplied or distributed.
-
E.
usesElectricalPlug
Indicates that one entity operates by being connected to another entity via an electrical plug.
- 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_69e7ab3a199c81909227cb964cacfe24 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 22, 2026, 8:07 a.m.