Triple
T24994165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ram |
E625522
|
entity |
| Predicate | predecessorBranding |
P1501
|
FINISHED |
| Object | Dodge Ram |
—
|
NE NERFINISHED |
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: Dodge Ram | Statement: [Ram, predecessorBranding, Dodge Ram]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorBranding Context triple: [Ram, predecessorBranding, Dodge Ram]
-
A.
successorBranding
Indicates that one brand has replaced or continued another brand as its subsequent or updated identity.
-
B.
formerBrand
chosen
Indicates that an entity was previously used or recognized as a brand for another entity but is no longer its current brand.
-
C.
successorBrandOwner
Indicates that one brand owner has taken over ownership or control of a brand from a previous brand owner, acting as its legal or commercial successor.
-
D.
successorPlatformBrand
Indicates that one platform brand directly follows and replaces another in a product or generational sequence.
-
E.
successorBrandScope
Indicates that one brand has replaced or followed another brand in scope, such as in market presence, ownership, or official continuity.
- 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 6:04 a.m.