Triple
T35305998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muskogee–Davis Regional Airport |
E1019636
|
entity |
| Predicate | runway 13/31 width (feet) |
P26238
|
FINISHED |
| Object | 150 |
—
|
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: 150 | Statement: [Muskogee–Davis Regional Airport, runway 13/31 width (feet), 150]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runway 13/31 width (feet) Context triple: [Muskogee–Davis Regional Airport, runway 13/31 width (feet), 150]
-
A.
runwayWidth
chosen
Indicates the measured width of a runway as a spatial dimension.
-
B.
runway13_31Usage
Indicates how runway 13/31 is used, such as the type, frequency, or conditions of its operational usage.
-
C.
runwayLength
Indicates the length of a runway associated with an airport or airfield.
-
D.
runway
Indicates a relationship where a runway serves as the takeoff and landing surface used by aircraft at an airport or airfield.
-
E.
runwayLengthUnit
Indicates the unit of measurement used to express the length of a runway in the relationship.
- 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:03 p.m.