Triple
T31114857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abbotsford International Airport |
E793055
|
entity |
| Predicate | runway01/19Surface |
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: [Abbotsford International Airport, runway01/19Surface, asphalt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runway01/19Surface Context triple: [Abbotsford International Airport, runway01/19Surface, asphalt]
-
A.
runwaySurface
chosen
Indicates the type or condition of the surface material that a runway is made of or covered with.
-
B.
runway
Indicates a relationship where a runway serves as the takeoff and landing surface used by aircraft at an airport or airfield.
-
C.
runway11_29Use
Indicates that runway 11/29 is being used for aircraft operations such as takeoffs or landings.
-
D.
runwayCharacteristic
Indicates a relationship where specific attributes or features are associated with 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 29, 2026, 9:04 p.m.