Triple
T29990307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canton Charge |
E761855
|
entity |
| Predicate | dissolvedAsCantonCharge |
P147396
|
FINISHED |
| Object | 2021 |
—
|
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: 2021 | Statement: [Canton Charge, dissolvedAsCantonCharge, 2021]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dissolvedAsCantonCharge Context triple: [Canton Charge, dissolvedAsCantonCharge, 2021]
-
A.
dissolvedDueTo
Indicates that a relationship, agreement, or entity came to an end as a result of a specified cause or event.
-
B.
dissolvedJurisdiction
chosen
Indicates that a jurisdiction or governing authority has been formally terminated, abolished, or ceased to exist.
-
C.
dissolvedAlongWith
Indicates that one entity ceased to exist, function, or operate at the same time and in conjunction with another entity.
-
D.
dissolvedInPart
Indicates that one substance is only partially dissolved in another, resulting in an incomplete or limited dissolution.
-
E.
dissolvedAs
Indicates that one entity ceased to exist or operate in its original form and was formally absorbed, merged, or reconstituted as another 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 6:38 p.m.