Triple
T9144228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Beach Airport |
E219406
|
entity |
| Predicate | hasTerminalDesign |
P21767
|
FINISHED |
| Object | open-air concourses |
—
|
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: open-air concourses | Statement: [Long Beach Airport, hasTerminalDesign, open-air concourses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTerminalDesign Context triple: [Long Beach Airport, hasTerminalDesign, open-air concourses]
-
A.
terminalDesign
Indicates a relationship where an entity is responsible for or characterized by the design or configuration of a terminal or terminal-like interface.
-
B.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
C.
isDesignedAs
Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
-
D.
isDesignedFor
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
-
E.
hasPassengerTerminalDesign
chosen
Indicates a design relationship in which one entity specifies or defines the passenger terminal layout, structure, or configuration of another entity.
- 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_69ca83e121dc81909912bd66953081c5 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca91548248190ae0b63edebf3d674 |
completed | April 1, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69cc6603ce8c8190bf6e8d6754bdec54 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:19 p.m.