Triple
T24311265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airport Terminal 3 Metro Station |
E612678
|
entity |
| Predicate | allowsLuggage |
P155519
|
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: [Airport Terminal 3 Metro Station, allowsLuggage, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsLuggage Context triple: [Airport Terminal 3 Metro Station, allowsLuggage, yes]
-
A.
hasLuggage
Indicates that an entity is carrying, possessing, or associated with one or more pieces of luggage.
-
B.
hasOnboardLuggageSpace
Indicates that an entity provides or includes dedicated space for carrying luggage on board.
-
C.
baggagePolicyType
Indicates the specific category or type of baggage policy that applies in a given travel or transportation context.
-
D.
hasBaggageClaim
Indicates that a location, typically a transportation hub, includes or provides a baggage claim area for retrieving luggage.
-
E.
providesExtraBaggage
Indicates that one entity offers or supplies additional baggage capacity or allowance to another entity.
- 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_69e2d7d91bb48190bc5377d17a85fb21 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2922a6afc8190b02cc2d185d15a45 |
completed | April 29, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69f1c45f45888190a9ccc225906c34bd |
completed | April 29, 2026, 8:42 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, 1:37 a.m.