Triple
T3592868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pago Pago International Airport |
E76066
|
entity |
| Predicate | runwayLength_05/23_m |
P6291
|
FINISHED |
| Object | 3048 |
—
|
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: 3048 | Statement: [Pago Pago International Airport, runwayLength_05/23_m, 3048]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runwayLength_05/23_m Context triple: [Pago Pago International Airport, runwayLength_05/23_m, 3048]
-
A.
runwayLength
chosen
Indicates the length of a runway associated with an airport or airfield.
-
B.
runwayWidth
Indicates the measured width of a runway as a spatial dimension.
-
C.
runway
Indicates a relationship where a runway serves as the takeoff and landing surface used by aircraft at an airport or airfield.
-
D.
hasRunwayLengthCategory
Indicates that an airport or airfield is associated with a specific categorical range of runway lengths (e.g., short, medium, long).
-
E.
runwayPerformance
Indicates the performance characteristics or behavior of an entity (such as an aircraft or vehicle) when operating on a runway, including factors like acceleration, deceleration, and required distances.
- 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_69ad85d8042081908af94a04c410dec0 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc15bbbcc81908d6cf95f8e70c6ca |
completed | March 8, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69adb83b66708190bb9d2f23d6fd308e |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:22 p.m.