Triple
T3845336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LAX Terminal 1 |
E93555
|
entity |
| Predicate | hasGateRange |
P51885
|
FINISHED |
| Object | Gates 9–18B |
—
|
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: Gates 9–18B | Statement: [LAX Terminal 1, hasGateRange, Gates 9–18B]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGateRange Context triple: [LAX Terminal 1, hasGateRange, Gates 9–18B]
-
A.
hasGate
Indicates that one entity possesses, includes, or is equipped with a gate as part of its structure or configuration.
-
B.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
C.
hasFaregates
Indicates that an entity is equipped with or contains faregates used to control or validate access, typically for paid entry.
-
D.
hasCityGateStatus
Indicates the status or condition of a city gate in relation to a given entity.
-
E.
hasAreaRange
Indicates that something’s area falls within a specified minimum-to-maximum range.
- 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_69aed96ce578819084ab16e3439976c9 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeebb77a488190be7fc2a1211f1f2d |
completed | March 9, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69aee750377c8190af70c79768c0edd8 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aee8d9b328819080158be59e5bcc97 |
completed | March 9, 2026, 3:35 p.m. |
Created at: March 9, 2026, 3:18 p.m.