Triple
T26237969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 13/31 |
E656220
|
entity |
| Predicate | principalRunwayOf |
P67502
|
FINISHED |
| Object | Pinto Martins – Fortaleza International 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: Pinto Martins – Fortaleza International Airport | Statement: [Runway 13/31, principalRunwayOf, Pinto Martins – Fortaleza International Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: principalRunwayOf Context triple: [Runway 13/31, principalRunwayOf, Pinto Martins – Fortaleza International Airport]
-
A.
usesRunwayOf
Indicates that one entity makes use of the runway that belongs to or is associated with another entity.
-
B.
runway
Indicates a relationship where a runway serves as the takeoff and landing surface used by aircraft at an airport or airfield.
-
C.
isRunwayOf
chosen
Indicates that a physical runway is a component or facility belonging to, used by, or officially associated with a particular airport or airfield.
-
D.
runwayName
Indicates the designated name or identifier assigned to a runway.
-
E.
runwayUsedAs
Indicates that a particular runway is being utilized for a specific purpose, role, or operational function.
- 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_69ee5b4c59a881909d9ee4fd013fffd5 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 26, 2026, 9:02 p.m.