Triple
T36830663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blood Tribe |
E910128
|
entity |
| Predicate | hasCollectiveLeadershipBody |
P132147
|
FINISHED |
| Object | Council |
—
|
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: Council | Statement: [Blood Tribe, hasCollectiveLeadershipBody, Council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollectiveLeadershipBody Context triple: [Blood Tribe, hasCollectiveLeadershipBody, Council]
-
A.
hasRepresentativeBody
Indicates that an entity is associated with or governed by a specific representative body that acts or decides on its behalf.
-
B.
hasRepresentativeBoard
Indicates that an entity is governed or overseen by a representative board acting on its behalf.
-
C.
hasCouncilStructure
chosen
Indicates that an entity is organized or governed according to a specific council-based structure or system.
-
D.
hasConsultativeBody
Indicates that an entity is associated with a consultative body that provides advice, recommendations, or guidance on its decisions or activities.
-
E.
conferringBody
Indicates the organization or authority that formally grants or bestows something, such as an award, degree, or title, upon a recipient.
- 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.