Triple
T26671374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Montenegro |
E672338
|
entity |
| Predicate | hasServiceFromAirport |
P6864
|
FINISHED |
| Object | Podgorica 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: Podgorica Airport | Statement: [Air Montenegro, hasServiceFromAirport, Podgorica Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServiceFromAirport Context triple: [Air Montenegro, hasServiceFromAirport, Podgorica Airport]
-
A.
servesAirportIATA
Indicates that a transportation service or facility operates routes to or from the airport identified by the given IATA code.
-
B.
servesAirport
chosen
Indicates that a transportation service or route provides access to and operates for a particular airport.
-
C.
servesAirportICAO
Indicates that a transportation service or facility operates routes to or from the airport identified by the given ICAO code.
-
D.
hasAirportAccessTo
Indicates that one location or entity has direct access to another via an airport connection or service.
-
E.
hasAirportRelatedFunction
Indicates that something performs a role, service, or activity specifically related to the operation, support, or functioning of an airport.
- 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_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 27, 2026, 3:13 a.m.