Triple
T25125653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pleso Airport |
E629386
|
entity |
| Predicate | hasNewPassengerTerminalOpened |
P74379
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Pleso Airport, hasNewPassengerTerminalOpened, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNewPassengerTerminalOpened Context triple: [Pleso Airport, hasNewPassengerTerminalOpened, 2017]
-
A.
newPassengerTerminalOpened
chosen
Indicates that a new passenger terminal has begun operations and is now open for use.
-
B.
hasNewTerminalOpened
Indicates that a new terminal facility has begun operation or become available at a given location or entity.
-
C.
hasPassengerTerminal
Indicates that one entity possesses or is equipped with a passenger terminal used for boarding, alighting, or handling passengers.
-
D.
hasPassengerTerminalFunction
Indicates that something serves the role or performs the function of a passenger terminal, supporting the handling and movement of passengers.
-
E.
hasPassengerTerminalSector
Indicates that a passenger terminal is divided into or associated with a specific sector or subsection within it.
- 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_69e2ff3288048190bd82c3b7f7bd0e62 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 18, 2026, 6:28 a.m.