Triple
T22919121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caleb Davis Bradham |
E568806
|
entity |
| Predicate | productRenamedOn |
P68192
|
FINISHED |
| Object | 1898 |
—
|
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: 1898 | Statement: [Caleb Davis Bradham, productRenamedOn, 1898]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productRenamedOn Context triple: [Caleb Davis Bradham, productRenamedOn, 1898]
-
A.
productRenamedAs
chosen
Indicates that a product previously known by one name is now identified or marketed under a new name.
-
B.
changedNameOn
Indicates that an entity altered or updated its name at a specific point in time or on a particular date.
-
C.
replacedInProduct
Indicates that one component or element in a product has been substituted or superseded by another component or element within that product.
-
D.
changedNameIn
Indicates that an entity has altered or adopted a different name within a specific context, time period, or jurisdiction.
-
E.
renamedDueTo
Indicates that one entity was renamed as a consequence of another specified cause, event, or condition.
- 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_69e2458d90c88190a58cead4e781ca6a |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f180d316188190901d9356c07110e3 |
completed | April 29, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:42 p.m.