Triple
T27252163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carleton County Council |
E687512
|
entity |
| Predicate | usedGovernmentType |
P80989
|
FINISHED |
| Object | county council system |
—
|
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: county council system | Statement: [Carleton County Council, usedGovernmentType, county council system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedGovernmentType Context triple: [Carleton County Council, usedGovernmentType, county council system]
-
A.
basedInGovernmentType
Indicates that an entity operates within or is associated with a government of a specified governmental system or type.
-
B.
targetGovernmentType
Indicates the form or system of governance that an entity is directed toward, associated with, or intended to influence.
-
C.
usedInGovernmentIn
Indicates that something is employed, applied, or functions within the context of a specific government or governmental system.
-
D.
implementedGovernmentType
chosen
Indicates the specific form of government that has been put into practice or adopted by an entity.
-
E.
laterGovernmentType
Indicates that one government type succeeds or replaces another at a later point in time.
- 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_69ef35567e808190a94458cd44ebff0c |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f626b71a748190be67fea2d48e6126 |
completed | May 2, 2026, 4:30 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 10:46 a.m.