Triple
T28067528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rover P5 |
E709295
|
entity |
| Predicate | P5EngineDisplacement |
P7998
|
FINISHED |
| Object | 3.0 litre |
—
|
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: 3.0 litre | Statement: [Rover P5, P5EngineDisplacement, 3.0 litre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: P5EngineDisplacement Context triple: [Rover P5, P5EngineDisplacement, 3.0 litre]
-
A.
availableEngineDisplacement
Indicates the range or specific values of engine displacement that are offered or applicable for a given entity.
-
B.
engineDisplacement
chosen
Indicates the total volume swept by all the pistons inside an engine’s cylinders during one complete cycle.
-
C.
designedDisplacement
Indicates the intended or specified amount of displacement (such as volume or weight moved) that something is engineered or planned to produce or accommodate.
-
D.
displacementPerCylinder
Indicates the volume of space displaced by the piston in a single cylinder during one complete stroke or cycle.
-
E.
pistons
Indicates a mechanical relationship where pistons convert pressure (often from combustion or fluid) into linear motion or vice versa within an engine or similar system.
- 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_69ef9b6eb6d88190a3fea236eb0f7bed |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6401cee508190a0dd02cb60d72f3b |
completed | May 2, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f637120c008190b2b5adf46f022e48 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8:43 p.m.