Triple
T1655671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sphinx International Airport |
E35792
|
entity |
| Predicate | hasBaggageClaim |
P30952
|
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: [Sphinx International Airport, hasBaggageClaim, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBaggageClaim Context triple: [Sphinx International Airport, hasBaggageClaim, yes]
-
A.
hasBaggageSystem
Indicates that an entity is equipped with or utilizes a baggage handling system.
-
B.
hasCustomsAndImmigration
Indicates that customs and immigration control services are present or provided at a given location or facility.
-
C.
hasCargoAirline
Indicates that one entity operates as a cargo airline for, or provides cargo air transport services to, another entity.
-
D.
baggagePolicySetBy
Indicates that a specific baggage policy is determined, defined, or controlled by a particular entity (such as an airline or service provider).
-
E.
hasPassengerHandling
Indicates that an entity is responsible for or involved in managing the processes and services related to handling passengers.
- 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_69a8860568888190a32cd9f70acbba42 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf3359ce48190803b322db8ad6027 |
completed | March 6, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69a907cff53c8190b424f088478d3e2c |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a99a4c3810819089d2dd0e23c8e46b |
completed | March 5, 2026, 2:59 p.m. |
Created at: March 4, 2026, 7:29 p.m.