Triple
T18432368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 4/22 (Texarkana Regional Airport) |
E450301
|
entity |
| Predicate | hasLengthMeters |
P25800
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [Runway 4/22 (Texarkana Regional Airport), hasLengthMeters, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLengthMeters Context triple: [Runway 4/22 (Texarkana Regional Airport), hasLengthMeters, 2012]
-
A.
approximateLengthInMeters
chosen
Indicates the estimated or roughly measured length of something expressed in meters.
-
B.
dimensionOfLength
Indicates that something represents or specifies a measurement along a single spatial extent (a length dimension).
-
C.
hasLengthFeet
Indicates that an entity possesses a length measured in feet.
-
D.
properLengthMeasuredIn
Indicates that the proper (intrinsic or rest-frame) length of an entity is expressed using a specified unit of measurement.
-
E.
hasMeter
Indicates that one entity possesses, uses, or is associated with a specific meter (a measuring device or metrical pattern).
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51b183adc8190987bc7749d0e673c |
completed | April 19, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:26 a.m.