Triple
T23148248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolls-Royce Dart |
E578251
|
entity |
| Predicate | poweredFirst |
P109257
|
FINISHED |
| Object | Vickers Viscount in airline service |
—
|
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: Vickers Viscount in airline service | Statement: [Rolls-Royce Dart, poweredFirst, Vickers Viscount in airline service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: poweredFirst Context triple: [Rolls-Royce Dart, poweredFirst, Vickers Viscount in airline service]
-
A.
poweredVersionOf
Indicates that one entity is a more powerful, enhanced, or upgraded version of another entity.
-
B.
primaryPower
Indicates that one entity serves as the main or dominant source of power or energy for another entity.
-
C.
powering
chosen
Indicates that one entity supplies energy or power that enables another entity to operate or function.
-
D.
powerBy
Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
-
E.
usesPowerFor
Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
- 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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18ecf9e9881908991ede784158f1e |
completed | April 29, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:01 p.m.