Triple
T27389519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 10/28 |
E691480
|
entity |
| Predicate | isInstrumentCapable |
P162653
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Runway 10/28, isInstrumentCapable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInstrumentCapable Context triple: [Runway 10/28, isInstrumentCapable, true]
-
A.
isInstrumentFor
Indicates that something is used as a tool or means to perform a particular action or achieve a specific outcome.
-
B.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
C.
isCapableOf
Indicates that an entity has the ability or capacity to perform a particular action or function.
-
D.
isStandardInInstrument
Indicates that something conforms to the usual or officially accepted form, configuration, or usage within a given instrument.
-
E.
supportedInstrument
Indicates that an entity provides compatibility with, or operational support for, a specified instrument.
- F. None of above. chosen
Provenance (4 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_69ef520386788190bc92cfcd97ebb67a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62cd1912c8190ab3f3288442115a4 |
completed | May 2, 2026, 4:56 p.m. |
Created at: April 27, 2026, 12:25 p.m.