Triple
T27450472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 23 |
E692423
|
entity |
| Predicate | hasMultipleInstancesWorldwide |
P88031
|
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 23, hasMultipleInstancesWorldwide, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultipleInstancesWorldwide Context triple: [Runway 23, hasMultipleInstancesWorldwide, true]
-
A.
hasGlobalDistribution
Indicates that the related entity occurs, operates, or is present across most or all regions of the world rather than being confined to a specific locality or region.
-
B.
hasGlobalReach
Indicates that an entity’s influence, operations, or impact extends across multiple countries or worldwide.
-
C.
usedWorldwide
Indicates that something is utilized or applied across many countries or regions around the world.
-
D.
isOfficialInMultipleContinents
Indicates that an entity holds an official status, role, or recognition in more than one continent.
-
E.
hasMultiplePhysicalInstances
chosen
Indicates that a single conceptual entity is realized or exists as more than one distinct physical instance.
- 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_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 27, 2026, 12:47 p.m.