Triple
T66536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oldsmobile Delmont 88 |
E1326
|
entity |
| Predicate | succeededByNameChange |
P2136
|
FINISHED |
| Object | dropping of Delmont name after 1968 |
—
|
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: dropping of Delmont name after 1968 | Statement: [Oldsmobile Delmont 88, succeededByNameChange, dropping of Delmont name after 1968]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: succeededByNameChange Context triple: [Oldsmobile Delmont 88, succeededByNameChange, dropping of Delmont name after 1968]
-
A.
nameChangeReason
chosen
Indicates the reason or justification for a change in an entity’s name.
-
B.
nameChangeDate
Indicates the date on which an entity’s name was officially changed.
-
C.
formerName
Indicates that an entity was previously known by a different name in the past.
-
D.
namedAfter
Indicates that one entity has been given its name in honor of, or derived from, another entity.
-
E.
commonName
Indicates that one entity is the commonly used or vernacular name by which the other entity is known.
- 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a2509b5a088190bb9d2b650aeb8bca |
completed | Feb. 28, 2026, 2:19 a.m. |
| PD | Predicate disambiguation | batch_69a24ea749788190bc17865171ff909a |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.