Triple
T27687949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rover SD1 |
E698080
|
entity |
| Predicate | motorsportEngine |
P56323
|
FINISHED |
| Object | 3.5 L Rover V8 |
—
|
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: 3.5 L Rover V8 | Statement: [Rover SD1, motorsportEngine, 3.5 L Rover V8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: motorsportEngine Context triple: [Rover SD1, motorsportEngine, 3.5 L Rover V8]
-
A.
engine
Indicates a relationship where something functions as, contains, or is driven by an engine as its source of mechanical power or propulsion.
-
B.
engineComponent
Indicates that one entity functions as a component or part of an engine in relation to another entity.
-
C.
enginePower
Indicates the power output produced by an engine, typically quantifying its capability to perform work or generate mechanical energy.
-
D.
engineTypeUsed
chosen
Indicates that a particular type of engine is employed or utilized in relation to a specified entity or system.
-
E.
engineTypeIncluded
Indicates that a specified engine type is included as part of, or supported within, another entity or configuration.
- 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63574d2388190839cd1061e3c9074 |
completed | May 2, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:50 p.m.