Triple
T27450465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 23 |
E692423
|
entity |
| Predicate | mayChangeTo |
P162410
|
FINISHED |
| Object | Runway 24 |
—
|
NE NERFINISHED |
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: Runway 24 | Statement: [Runway 23, mayChangeTo, Runway 24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayChangeTo Context triple: [Runway 23, mayChangeTo, Runway 24]
-
A.
mayChangeTo
chosen
Indicates that one state, condition, or value is allowed or able to transition into another.
-
B.
canChangeIn
Indicates that one entity is capable of undergoing alteration, transformation, or variation within the context or influence of another entity or condition.
-
C.
mayReverse
Indicates that an action, process, or state can be undone or returned to a previous condition.
-
D.
mayAdvanceTo
Indicates that one entity is permitted or eligible to progress, move, or be promoted to another specified state, level, or position.
-
E.
mayAdapt
Indicates that one entity is permitted or allowed to modify, adjust, or alter another 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_69ef5206c9248190b5975c2a7f9d229c |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62dc5a7948190b74476634f251a0e |
completed | May 2, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 12:47 p.m.