Triple
T34660850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1969 Dodge Charger |
E890100
|
entity |
| Predicate | notableEngineBranding |
P18926
|
FINISHED |
| Object | 426 Hemi |
E250911
|
NE 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: 426 Hemi | Statement: [1969 Dodge Charger, notableEngineBranding, 426 Hemi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEngineBranding Context triple: [1969 Dodge Charger, notableEngineBranding, 426 Hemi]
-
A.
notableBrandElement
Indicates that one entity is a significant or distinguishing brand-related feature, component, or asset of another entity.
-
B.
notableEngineType
Indicates that an entity is particularly recognized for using or being associated with a specific type of engine.
-
C.
notableManufacturer
Indicates that an entity is a well-known or prominent producer or maker of another entity.
-
D.
engineBrand
Indicates that one entity is the brand or manufacturer of the engine used by another entity.
-
E.
notableEngineFamily
chosen
Indicates that one entity is a well-known or significant engine family associated with the other entity.
- F. None of above.
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_69f349d906bc8190b2efd9eff237d94b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3749002278819092de3654d39c20cc |
completed | June 21, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:04 a.m.