Triple
T9694674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tribal Council |
E234616
|
entity |
| Predicate | hasDecisionMakingPowerIn |
P34807
|
FINISHED |
| Object | tribal administration |
—
|
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: tribal administration | Statement: [Tribal Council, hasDecisionMakingPowerIn, tribal administration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDecisionMakingPowerIn Context triple: [Tribal Council, hasDecisionMakingPowerIn, tribal administration]
-
A.
hasDecisionMakingPower
chosen
Indicates that one entity possesses the authority or ability to make decisions that affect another entity or a given context.
-
B.
hasDecisionMaker
Indicates that one entity serves as the decision-making authority or agent for another entity.
-
C.
hasExecutiveAuthority
Indicates that one entity holds formal decision-making and managerial power over an organization, group, or process.
-
D.
hasLegislativePower
Indicates that an entity possesses the authority to create, amend, or repeal laws within a given jurisdiction or governing framework.
-
E.
hasVetoPower
Indicates that one entity possesses the authority to unilaterally reject or block decisions, actions, or proposals made by another entity or group.
- 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_69ca84cb580c8190a7e5f4b3bcdaf2a4 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d348868819083aec7a5da8c455b |
completed | April 1, 2026, 10:33 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b840f081909f66bf0b66d17d9b |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:17 p.m.