Triple
T25125672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MZLZ d.d. |
E629387
|
entity |
| Predicate | operatesMainInternationalAirportOf |
P38515
|
FINISHED |
| Object | Croatia |
—
|
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: Croatia | Statement: [MZLZ d.d., operatesMainInternationalAirportOf, Croatia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesMainInternationalAirportOf Context triple: [MZLZ d.d., operatesMainInternationalAirportOf, Croatia]
-
A.
operatesAirport
chosen
Indicates that one entity manages and runs the operations of an airport.
-
B.
isOnlyInternationalAirportOf
Indicates that an airport is the single, unique international airport serving a particular city, region, or country.
-
C.
servesAsPrimaryAirportOperatorForCity
Indicates that an entity functions as the main organization responsible for operating the primary airport serving a particular city.
-
D.
hasInternationalAirport
Indicates that a place possesses an airport that handles international flights and services cross-border air traffic.
-
E.
isMainAirportStopFor
Indicates that a given airport serves as the primary or principal stop for a specified route, service, or transportation connection.
- 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_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 18, 2026, 6:28 a.m.