Triple
T3592896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pago Pago International Airport |
E76066
|
entity |
| Predicate | runwayLights |
P13444
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Pago Pago International Airport, runwayLights, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runwayLights Context triple: [Pago Pago International Airport, runwayLights, yes]
-
A.
hasRunwayLighting
chosen
Indicates that a runway is equipped with lighting systems to aid visibility and operations, typically during low-light or night conditions.
-
B.
runwayPresence
Indicates the existence or availability of a runway at or associated with the referenced location or facility.
-
C.
runwaySurface
Indicates the type or condition of the surface material that a runway is made of or covered with.
-
D.
runway
Indicates a relationship where a runway serves as the takeoff and landing surface used by aircraft at an airport or airfield.
-
E.
runwayEnd
Indicates that one entity represents the end point or terminus of a runway associated with the other entity.
- 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.