Triple
T7541425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 5 |
E178282
|
entity |
| Predicate | hasNumericFormat |
P11851
|
FINISHED |
| Object | two-digit runway marking “05” on pavement |
—
|
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: two-digit runway marking “05” on pavement | Statement: [Runway 5, hasNumericFormat, two-digit runway marking “05” on pavement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumericFormat Context triple: [Runway 5, hasNumericFormat, two-digit runway marking “05” on pavement]
-
A.
hasNumericalValue
Indicates that an entity is associated with a specific numeric quantity or measurement.
-
B.
hasFormatElement
Indicates that one entity includes, is composed of, or is associated with a specific structural or formatting component of its overall format.
-
C.
hasFormatCurrent
Indicates that an entity is available or expressed in the currently used or most up-to-date format.
-
D.
hasDigitSet
Indicates that an entity is associated with a specific set or collection of digits.
-
E.
hasDigitCount
chosen
Indicates that one entity has a total number of digits equal to the value specified by the other entity.
- 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_69c69f2be3888190a6667a27f8f195e9 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8750f80819088ddfb7a5580b5df |
completed | March 27, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69c6f4daad6c8190af2b8ae88d2c8cb7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:48 p.m.