Triple
T1670020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | York, Ontario |
E36102
|
entity |
| Predicate | amalgamationEvent |
P176
|
FINISHED |
| Object | 1998 Toronto municipal amalgamation |
—
|
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: 1998 Toronto municipal amalgamation | Statement: [York, Ontario, amalgamationEvent, 1998 Toronto municipal amalgamation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: amalgamationEvent Context triple: [York, Ontario, amalgamationEvent, 1998 Toronto municipal amalgamation]
-
A.
wasUnifiedWith
Indicates that two or more previously separate entities were brought together to form a single unified whole.
-
B.
foundedByMergerOf
Indicates that an entity was created through the merger or combination of two or more predecessor entities.
-
C.
dissolvedByMerger
Indicates that an entity ceased to exist as an independent entity because it was legally combined into another entity through a merger.
-
D.
mergerType
Indicates the specific kind or category of merger relationship that exists between the involved entities.
-
E.
mergerYear
chosen
Indicates the year in which two or more entities formally merged into a single entity.
- 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_69a8861286808190939afff3ce8ee31e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab272a653481908f48aa1eed5de8a4 |
completed | March 6, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69aa61b2f6288190b2348ef7d7e4672d |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.