Triple
T27450466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 23 |
E692423
|
entity |
| Predicate | canBeRenumberedDueTo |
P77336
|
FINISHED |
| Object | magnetic variation shift |
—
|
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: magnetic variation shift | Statement: [Runway 23, canBeRenumberedDueTo, magnetic variation shift]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeRenumberedDueTo Context triple: [Runway 23, canBeRenumberedDueTo, magnetic variation shift]
-
A.
canBeRenumberedTo
Indicates that one entity’s identifiers or numbering scheme can be systematically changed to match or correspond to another set of identifiers or numbering.
-
B.
canBeRenumberedFrom
Indicates that one entity’s numbering or identifier sequence is allowed to be changed starting from the numbering or identifier of another entity.
-
C.
mayBeRenumbered
Indicates that an entity’s identifier or numbering is allowed to change under certain conditions.
-
D.
renumberingCondition
chosen
Indicates the condition or criteria under which elements are reassigned new numbers or identifiers.
-
E.
renumbered
Indicates that an entity’s identifying number or sequence position has been changed to a new numbering scheme.
- 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_69ef5206c9248190b5975c2a7f9d229c |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 27, 2026, 12:47 p.m.