Triple
T25866504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concourse E |
E651630
|
entity |
| Predicate | hasCustomsAndImmigrationAccess |
P7852
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Concourse E, hasCustomsAndImmigrationAccess, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCustomsAndImmigrationAccess Context triple: [Concourse E, hasCustomsAndImmigrationAccess, true]
-
A.
hasCustomsAndImmigration
chosen
Indicates that customs and immigration control services are present or provided at a given location or facility.
-
B.
hasCustomsCheckpoint
Indicates that a location or route includes an official customs inspection point where goods, vehicles, or people are checked for compliance with border regulations.
-
C.
hasBorderFacilityAccess
Indicates that an entity is permitted to enter, use, or operate within a designated border facility or checkpoint.
-
D.
hasBorderControlStatus
Indicates the type or condition of border control that applies to a given entity or location.
-
E.
hasConsularEntranceOn
Indicates that a consular facility or office has an entrance located on a specified street, side, or access point.
- 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_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 22, 2026, 8:07 a.m.