Triple
T26814054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminal 2 (Iași International Airport) |
E672075
|
entity |
| Predicate | locatedInCountryOfServedAirport |
P122681
|
FINISHED |
| Object | Romania |
—
|
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: Romania | Statement: [Terminal 2 (Iași International Airport), locatedInCountryOfServedAirport, Romania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInCountryOfServedAirport Context triple: [Terminal 2 (Iași International Airport), locatedInCountryOfServedAirport, Romania]
-
A.
isLocatedAtAirportServingCity
Indicates that something is situated at an airport that provides service to a particular city.
-
B.
basedInAirport
Indicates that an entity has its primary location, operations, or headquarters situated at a specific airport.
-
C.
locatedInCurrentCountry
chosen
Indicates that an entity is situated within the geographic boundaries of the country in which it is presently found.
-
D.
isLocatedAtAirportType
Indicates that one entity is situated at, or associated with, an airport of a specified type (e.g., international, regional, military).
-
E.
servedByAirportInOriginCity
Indicates that the origin city of a trip or route is served by a particular 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_69eeb3225a3c8190aaf6746efeded2f3 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
Created at: April 27, 2026, 4:31 a.m.