Triple
T7226586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tim Hortons |
E154795
|
entity |
| Predicate | demergerDate |
P36464
|
FINISHED |
| Object | 2006 |
—
|
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: 2006 | Statement: [Tim Hortons, demergerDate, 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demergerDate Context triple: [Tim Hortons, demergerDate, 2006]
-
A.
divestitureDate
chosen
Indicates the date on which an entity formally disposes of, sells, or otherwise relinquishes ownership or control of an asset, business unit, or investment.
-
B.
liquidationDate
Indicates the date on which an entity is formally wound up, dissolved, or its assets are converted to cash in a liquidation process.
-
C.
consolidationDate
Indicates the date on which multiple entities, records, or accounts are formally combined into a single consolidated whole.
-
D.
deFactoTransferDate
Indicates the date on which control or ownership is effectively transferred in practice, regardless of the formal or legal transfer date.
-
E.
ceaseToExistDecisionDate
Indicates the date on which a formal decision was made that something will cease to exist or be terminated.
- 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_69c68811dd1c8190ac460bb39e64e1f0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6e9de21e081908f30700f6211c5ef |
completed | March 27, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69c6e761b7fc8190857794d78af1b468 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:54 p.m.