Triple
T8607971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Detroit Diesel V8 |
E203849
|
entity |
| Predicate | productionCategory |
P83850
|
FINISHED |
| Object | heavy-duty diesel engine |
—
|
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: heavy-duty diesel engine | Statement: [Detroit Diesel V8, productionCategory, heavy-duty diesel engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productionCategory Context triple: [Detroit Diesel V8, productionCategory, heavy-duty diesel engine]
-
A.
productionBy
Indicates that something is created, manufactured, or generated by a particular agent, organization, or process.
-
B.
productionElement
Indicates that one entity functions as a component, ingredient, or constituent used in the creation, manufacture, or production of another entity.
-
C.
produces
Indicates that one entity creates, generates, or yields another entity as a result or output.
-
D.
productionBase
Indicates a relationship where one entity serves as the primary site, facility, or foundation used for producing or manufacturing something for another entity.
-
E.
componentTypeProduced
Indicates that one entity produces or manufactures a specific type of component as an output of its activity or process.
- F. None of above. chosen
Provenance (4 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46ec301881908ce148a3f07069fe |
completed | March 31, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cc454eb2908190acf0e4336bc67e7b |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc46c330bc8190a9b644078881c6ff |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:25 p.m.