Triple
T24217791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capital Region |
E601353
|
entity |
| Predicate | hasDomesticAirport |
P89290
|
FINISHED |
| Object | Reykjavík 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: Reykjavík Airport | Statement: [Capital Region, hasDomesticAirport, Reykjavík Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDomesticAirport Context triple: [Capital Region, hasDomesticAirport, Reykjavík Airport]
-
A.
isDomesticAirport
chosen
Indicates that an airport primarily handles flights within the same country, rather than international routes.
-
B.
hasInternationalAirport
Indicates that a place possesses an airport that handles international flights and services cross-border air traffic.
-
C.
hasRegionalAirport
Indicates that a place or region possesses or is served by a regional airport.
-
D.
isOnlyInternationalAirportOf
Indicates that an airport is the single, unique international airport serving a particular city, region, or country.
-
E.
isMajorDomesticAirportCode
Indicates that an airport code belongs to a major domestic airport within a given country or region.
- 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_69e29537ca548190b94a37ebe1977caf |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f2820a80ec8190bd11f08f7733843d |
completed | April 29, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:58 p.m.