Triple
T30292014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolls-Royce SZ platform |
E770403
|
entity |
| Predicate | engineTypeSupported |
P17976
|
FINISHED |
| Object | Rolls-Royce–Bentley L-series V8 engine |
—
|
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: Rolls-Royce–Bentley L-series V8 engine | Statement: [Rolls-Royce SZ platform, engineTypeSupported, Rolls-Royce–Bentley L-series V8 engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineTypeSupported Context triple: [Rolls-Royce SZ platform, engineTypeSupported, Rolls-Royce–Bentley L-series V8 engine]
-
A.
engineTypeIncluded
Indicates that a specified engine type is included as part of, or supported within, another entity or configuration.
-
B.
engineTypeUsed
Indicates that a particular type of engine is employed or utilized in relation to a specified entity or system.
-
C.
testedEngineType
Indicates that an engine of a specified type has been subjected to a test or evaluation.
-
D.
engineTypeBuilt
Indicates that a specific type of engine has been constructed or manufactured by a particular entity.
-
E.
offeredEngineType
chosen
Indicates that a particular type of engine is made available or provided as an option in a given context.
- 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_69f224875c288190a9b96b975006ec4a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6813474208190b3e2f0ad7d2b9aab |
completed | May 2, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:47 p.m.