Triple
T17503842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waco Regional Airport |
E426259
|
entity |
| Predicate | runway1/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: [Waco Regional Airport, runway1/19Surface, asphalt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runway1/19Surface Context triple: [Waco Regional Airport, runway1/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.
runwayCharacteristic
Indicates a relationship where specific attributes or features are associated with a runway.
-
D.
runway11_29Use
Indicates that runway 11/29 is being used for aircraft operations such as takeoffs or landings.
-
E.
runwayInformationAvailableIn
Indicates that information about a runway is available within or through a specified medium, source, or context.
- 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e45213a0e88190ac183d87ec088e86 |
completed | April 19, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f5fbcc8190a6ea9639bf5650da |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.