Triple
T29990306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canton Charge |
E761855
|
entity |
| Predicate | foundedAsCantonCharge |
P192774
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Canton Charge, foundedAsCantonCharge, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsCantonCharge Context triple: [Canton Charge, foundedAsCantonCharge, 2011]
-
A.
establishedAsCanton
Indicates that an entity was formally created or designated as a canton within an administrative or political system.
-
B.
hasCanton
Indicates that an entity is administratively divided into, or associated with, a specific canton.
-
C.
sourceCanton
Indicates the canton from which something or someone originates or is sourced.
-
D.
joinedCanton
Indicates that an entity became a member of, or was incorporated into, a specific canton.
-
E.
denotesCanton
Indicates that one entity is the canton (administrative subdivision) to which another entity belongs or with which it is associated.
- F. None of above. chosen
Provenance (4 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_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
| PDg | Predicate description generation | batch_69fd2a2095f88190bfcbcb2973516ffc |
completed | May 8, 2026, 12:11 a.m. |
Created at: April 29, 2026, 6:38 p.m.