Triple
T14790312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KPLN |
E347635
|
entity |
| Predicate | terminalAmenities |
P79291
|
FINISHED |
| Object | baggage claim |
—
|
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: baggage claim | Statement: [KPLN, terminalAmenities, baggage claim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminalAmenities Context triple: [KPLN, terminalAmenities, baggage claim]
-
A.
amenitiesInclude
chosen
Indicates that a place or facility provides or contains specific amenities as part of its features.
-
B.
amenity
Indicates that one entity provides a useful facility, service, or feature that enhances the convenience or comfort of another entity.
-
C.
hasGoodsFacilities
Indicates that a location or entity is equipped with facilities for handling, storing, or processing goods or cargo.
-
D.
hasDockingFacilities
Indicates that one entity provides or is equipped with docking facilities for another entity.
-
E.
userFacility
Indicates a relationship where a user is associated with, has access to, or operates within a particular facility.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decd5d134c819080ee788b2e34163a |
completed | April 14, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69de8c090d1081909b5a9bf437499d6c |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.