Triple
T31865433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piikani 147 |
E813436
|
entity |
| Predicate | confederacy |
P3193
|
FINISHED |
| Object | Blackfoot Confederacy |
—
|
NE NERFINISHED |
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: Blackfoot Confederacy | Statement: [Piikani 147, confederacy, Blackfoot Confederacy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confederacy Context triple: [Piikani 147, confederacy, Blackfoot Confederacy]
-
A.
joinedConfederateStatesOfAmerica
Indicates that an entity became a member of, or formally aligned itself with, the Confederate States of America.
-
B.
formerConfederation
Indicates that an entity was previously part of a confederation but is no longer a member.
-
C.
confederateInitiative
Indicates that an entity initiates or undertakes an action in coordination or alliance with others as part of a confederate effort.
-
D.
confederation
chosen
Indicates a formal union or alliance between multiple entities that retain their individual autonomy while cooperating under a shared framework or agreement.
-
E.
positionWithinConfederacy
Indicates that one entity holds a specific role, rank, or status within a confederated group or alliance of entities.
- 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_69f348ecb07481909c8f72619131b115 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 30, 2026, 11:53 p.m.