Triple
T30304119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Detroit Diesel 6V53 |
E770731
|
entity |
| Predicate | boreFamily |
P169065
|
FINISHED |
| Object | 53 series |
—
|
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: 53 series | Statement: [Detroit Diesel 6V53, boreFamily, 53 series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boreFamily Context triple: [Detroit Diesel 6V53, boreFamily, 53 series]
-
A.
bore
Indicates that one entity caused another entity to feel uninterested, tired, or lacking in engagement.
-
B.
hasBoreType
Indicates that an entity is characterized by or associated with a specific type of bore (e.g., cylindrical, tapered, rifled).
-
C.
hasBore
Indicates that one object possesses or is characterized by a specific bore, such as the internal diameter of a tube, pipe, or barrel.
-
D.
numberOfBores
Indicates the relationship specifying how many bores (e.g., cylindrical holes or channels) are present in or associated with an object.
-
E.
basedOnFamilyOf
Indicates that one entity is derived from, modeled after, or determined by the family, lineage, or familial characteristics of another entity.
- 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68166930881909608eece2bc5f055 |
completed | May 2, 2026, 10:57 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 29, 2026, 7:49 p.m.