Triple
T16481294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 02/20 (Carriel Sur International Airport) |
E400323
|
entity |
| Predicate | length (meters) |
P266
|
FINISHED |
| Object | 2400 |
—
|
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: 2400 | Statement: [Runway 02/20 (Carriel Sur International Airport), length (meters), 2400]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: length (meters) Context triple: [Runway 02/20 (Carriel Sur International Airport), length (meters), 2400]
-
A.
dimensionOfLength
Indicates that something represents or specifies a measurement along a single spatial extent (a length dimension).
-
B.
approximateLengthInMeters
Indicates the estimated or roughly measured length of something expressed in meters.
-
C.
length
chosen
Indicates a measurement relationship where a value specifies how long something is from one end to the other.
-
D.
lengthInKm
Indicates that one entity specifies the length or distance of another entity measured in kilometers.
-
E.
dimensions_km
Indicates the physical size or extent of something measured in kilometers, typically specifying one or more linear dimensions (e.g., length, width, height).
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e02b2c881909576a23bfbd3123c |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e22706b0588190a48a951c5211a617 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:13 a.m.