Triple
T30054835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paro District |
E763696
|
entity |
| Predicate | hasCountryOnlyInternationalAirport |
P105065
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
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: true | Statement: [Paro District, hasCountryOnlyInternationalAirport, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCountryOnlyInternationalAirport Context triple: [Paro District, hasCountryOnlyInternationalAirport, true]
-
A.
isOnlyInternationalAirportOf
chosen
Indicates that an airport is the single, unique international airport serving a particular city, region, or country.
-
B.
hasInternationalAirport
Indicates that a place possesses an airport that handles international flights and services cross-border air traffic.
-
C.
isInternationalAirportCode
Indicates that a given code designates an airport in the standardized international airport coding system (such as IATA or ICAO).
-
D.
isDomesticAirport
Indicates that an airport primarily handles flights within the same country, rather than international routes.
-
E.
hasRegionalAirport
Indicates that a place or region possesses or is served by a regional 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00c8e617548190bba4cdfbb6f512e0 |
completed | May 10, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_6a00c7e816b88190bd40f5ea2a768c8b |
completed | May 10, 2026, 6:01 p.m. |
Created at: April 29, 2026, 6:56 p.m.