Triple
T6792635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anishinabek |
E155969
|
entity |
| Predicate | hasTraditionalGovernance |
P35306
|
FINISHED |
| Object | clan 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: clan system | Statement: [Anishinabek, hasTraditionalGovernance, clan system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalGovernance Context triple: [Anishinabek, hasTraditionalGovernance, clan system]
-
A.
hasTraditionalInstitutions
chosen
Indicates that an entity possesses or is associated with long-established, customary social, cultural, or governance institutions.
-
B.
hasTraditionalCapital
Indicates that an entity serves or is recognized as the traditional or historical capital of another entity.
-
C.
hasHistoricalGovernmentForm
Indicates that an entity has, at some point in the past, been governed under a particular form or system of government.
-
D.
hasBiStateGovernance
Indicates that an entity is governed jointly or alternately by two distinct state-level authorities or governments.
-
E.
governedWithinTradition
Indicates that an entity’s actions, decisions, or organization are regulated or constrained according to a particular established tradition or customary framework.
- 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_69c6881770fc8190972b2906390380f5 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2af6f908190809e39b73894e513 |
completed | March 27, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d0979ce0819094678896da4e3169 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:15 p.m.