Triple
T27997235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rover 600 |
E707044
|
entity |
| Predicate | trimMaterials |
P113786
|
FINISHED |
| Object | leather (on higher trims) |
—
|
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: leather (on higher trims) | Statement: [Rover 600, trimMaterials, leather (on higher trims)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trimMaterials Context triple: [Rover 600, trimMaterials, leather (on higher trims)]
-
A.
hasTrimMaterial
chosen
Indicates that one entity uses or features a particular material specifically for its trim or edging components.
-
B.
traditionalMaterial
Indicates that something is made from, incorporates, or is characterized by materials associated with long-established or customary practices.
-
C.
featuresMaterialFrom
Indicates that one entity incorporates, contains, or is composed of material originating from another entity.
-
D.
trimFeatures
Indicates that certain features or attributes of an entity are reduced, removed, or cut down, typically to simplify or optimize it.
-
E.
destroyedMaterial
Indicates that one entity has caused the damage, ruin, or elimination of another entity or material.
- 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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63fd79e4c8190af9263b679e5ff07 |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 7:54 p.m.