Triple
T1228508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TJSJ |
E26380
|
entity |
| Predicate | hasPassengerBoardingBridges |
P18241
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [TJSJ, hasPassengerBoardingBridges, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPassengerBoardingBridges Context triple: [TJSJ, hasPassengerBoardingBridges, yes]
-
A.
hasBoardingGatesFor
Indicates that a location or facility provides designated boarding gates used for embarking passengers onto specific transportation services (such as flights or trains).
-
B.
hasPassengerTerminal
Indicates that one entity possesses or is equipped with a passenger terminal used for boarding, alighting, or handling passengers.
-
C.
hasPassengerHandling
Indicates that an entity is responsible for or involved in managing the processes and services related to handling passengers.
-
D.
hasRunwayAccessVia
Indicates that an entity has access to a runway by means of a specified connecting route, facility, or intermediary.
-
E.
hasBoardingType
chosen
Indicates the specific manner or method by which an entity is boarded or accessed (e.g., how passengers or items are taken on).
- 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_69a49484688c8190a1bf285eb396a8b6 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be3c5d4c819087f9e9e37204c3be |
completed | March 1, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69a4bb65d61c8190bf0424ea0019a98b |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.