Triple
T35156984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buick Somerset |
E1015148
|
entity |
| Predicate | laterRenamedOrMerged |
P102205
|
FINISHED |
| Object | Buick Skylark |
—
|
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: Buick Skylark | Statement: [Buick Somerset, laterRenamedOrMerged, Buick Skylark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterRenamedOrMerged Context triple: [Buick Somerset, laterRenamedOrMerged, Buick Skylark]
-
A.
wereRenamedAs
Indicates that one entity previously had a different name and was subsequently given or adopted the other entity as its new name.
-
B.
wasRenamedIn
Indicates that an entity changed its name to a different one at or during a specific time or event.
-
C.
laterMergedWith
chosen
Indicates that one entity was combined into and became part of another entity at a subsequent point in time.
-
D.
relocatedAndRenamed
Indicates that an entity has moved from one location to another and changed its name as part of that move.
-
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_69f76ddb3a708190b521ba2970b17178 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0058c341ac8190825067dc25158839 |
completed | May 10, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_6a005857249c81908b27587b84d84dbb |
completed | May 10, 2026, 10:05 a.m. |
Created at: May 3, 2026, 4:02 p.m.