Triple
T7634427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ljubljana Jože Pučnik Airport |
E172837
|
entity |
| Predicate | passengerTerminalType |
P77457
|
FINISHED |
| Object | single main passenger terminal |
—
|
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: single main passenger terminal | Statement: [Ljubljana Jože Pučnik Airport, passengerTerminalType, single main passenger terminal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passengerTerminalType Context triple: [Ljubljana Jože Pučnik Airport, passengerTerminalType, single main passenger terminal]
-
A.
hasPassengerTerminal
Indicates that one entity possesses or is equipped with a passenger terminal used for boarding, alighting, or handling passengers.
-
B.
hasPassengerTerminalFunction
Indicates that something serves the role or performs the function of a passenger terminal, supporting the handling and movement of passengers.
-
C.
stationType
Indicates the specific category or classification of a station based on its function, services, or operational characteristics.
-
D.
hasPassengerTerminalFacilities
Indicates that an entity provides facilities or infrastructure specifically intended for handling and serving passengers.
-
E.
hasPassengerTerminalDesign
Indicates a design relationship in which one entity specifies or defines the passenger terminal layout, structure, or configuration of 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_69c69952849881908fdcea7a93bfc307 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6faa72f2881908479049dd8d181a4 |
completed | March 27, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e8cadc8190b7977fcd213954dd |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f574d8a8819095749518dad13791 |
completed | March 27, 2026, 9:24 p.m. |
Created at: March 27, 2026, 3:57 p.m.