Triple
T4577769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BNA |
E101779
|
entity |
| Predicate | hasPassengerAmenities |
P38302
|
FINISHED |
| Object | retail shops |
—
|
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: retail shops | Statement: [BNA, hasPassengerAmenities, retail shops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPassengerAmenities Context triple: [BNA, hasPassengerAmenities, retail shops]
-
A.
hasPassengerServicesTo
Indicates that a transportation provider operates passenger services connecting one location or entity to another.
-
B.
hasPassengerArea
Indicates that an object or vehicle includes a designated area intended for carrying passengers.
-
C.
hasSpectatorAmenities
Indicates that a place or facility provides amenities or features intended for the comfort or convenience of spectators.
-
D.
hasPassengerTerminalFacilities
chosen
Indicates that an entity provides facilities or infrastructure specifically intended for handling and serving passengers.
-
E.
hasSeating
Indicates that one entity provides or contains seating capacity or seating arrangements for 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_69bd43d4ce208190b53158c882b222e3 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd58e2a1808190be4582d5b3003d6c |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5228b70c8190ac48705e35a710c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.