Triple
T31714292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wolastoqiyik |
E809410
|
entity |
| Predicate | confederacyRole |
P156726
|
FINISHED |
| Object | ally within the Wabanaki Confederacy |
—
|
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: ally within the Wabanaki Confederacy | Statement: [Wolastoqiyik, confederacyRole, ally within the Wabanaki Confederacy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confederacyRole Context triple: [Wolastoqiyik, confederacyRole, ally within the Wabanaki Confederacy]
-
A.
positionWithinConfederacy
Indicates that one entity holds a specific role, rank, or status within a confederated group or alliance of entities.
-
B.
confederationRole
chosen
Indicates the specific role or function an entity holds within a confederation or confederated arrangement.
-
C.
combatantConfederate
Indicates that an entity participates as a combatant on the Confederate side in a conflict or war.
-
D.
confederateInitiative
Indicates that an entity initiates or undertakes an action in coordination or alliance with others as part of a confederate effort.
-
E.
confederateArmyComponent
Indicates that one entity functions as a constituent unit, formation, or subpart of the Confederate army.
- 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_69f348df4e048190a4a5a9932ada78d6 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 30, 2026, 11:16 p.m.