Triple
T3202746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mataveri International Airport |
E67087
|
entity |
| Predicate | runwayExtendedFor |
P46123
|
FINISHED |
| Object | long-range aircraft operations |
—
|
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: long-range aircraft operations | Statement: [Mataveri International Airport, runwayExtendedFor, long-range aircraft operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runwayExtendedFor Context triple: [Mataveri International Airport, runwayExtendedFor, long-range aircraft operations]
-
A.
runway
Indicates a relationship where a runway serves as the takeoff and landing surface used by aircraft at an airport or airfield.
-
B.
runwayWidth
Indicates the measured width of a runway as a spatial dimension.
-
C.
runwaySharedBy
Indicates that the same runway is used jointly by multiple entities, such as aircraft, airlines, or airports.
-
D.
hasRunwayType
Indicates that an airport or airfield has a runway of a specified type or surface classification.
-
E.
usesRunwayOf
Indicates that one entity makes use of the runway that belongs to or is associated with another entity.
- F. None of above. chosen
Provenance (4 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_69ad8589bd988190afa7ed2bdffb7b33 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada9b188a88190b7b5e9b3be9410db |
completed | March 8, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69ad9e078f7c8190813d9fcb4f5071fb |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f9259c8190afbc5ad0fa55436b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:07 p.m.