Triple
T14361496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lomé–Tokoin International Airport |
E356113
|
entity |
| Predicate | runwaySurface_04_22 |
P422
|
FINISHED |
| Object | asphalt |
—
|
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: asphalt | Statement: [Lomé–Tokoin International Airport, runwaySurface_04_22, asphalt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runwaySurface_04_22 Context triple: [Lomé–Tokoin International Airport, runwaySurface_04_22, asphalt]
-
A.
runwaySurface
chosen
Indicates the type or condition of the surface material that a runway is made of or covered with.
-
B.
runwayCharacteristic
Indicates a relationship where specific attributes or features are associated with a runway.
-
C.
runwayWidth
Indicates the measured width of a runway as a spatial dimension.
-
D.
runwayPresence
Indicates the existence or availability of a runway at or associated with the referenced location or facility.
-
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_69d82790a7e08190877e2d349b2e8d8e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8fabec088190bd8128371b29e958 |
completed | April 14, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69de2a9cb3e081909f6b33fdd939bb9e |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:15 a.m.