Triple
T26671356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Montenegro |
E672338
|
entity |
| Predicate | secondaryBaseOfOperations |
P8522
|
FINISHED |
| Object | Tivat Airport |
—
|
NE NERFINISHED |
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: Tivat Airport | Statement: [Air Montenegro, secondaryBaseOfOperations, Tivat Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryBaseOfOperations Context triple: [Air Montenegro, secondaryBaseOfOperations, Tivat Airport]
-
A.
secondaryHeadquartersLocation
Indicates the location where an organization maintains a secondary (non-primary) headquarters.
-
B.
secondaryHub
chosen
Indicates that an entity functions as a secondary or backup hub in relation to a primary hub within a network or system.
-
C.
secondaryGeographicFocus
Indicates a secondary or less primary geographic area that is also a focus or target of the entity’s activities, influence, or relevance.
-
D.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
E.
hasBaseOfOperations
Indicates that an entity uses a particular location as its primary place of operation or activity.
- 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_69eecda00a9c8190b2691f4d89db03b6 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 27, 2026, 3:13 a.m.