Triple
T36361727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shawnee |
E895509
|
entity |
| Predicate | formedConfederacyEfforts |
P117976
|
FINISHED |
| Object | Tecumseh’s 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: Tecumseh’s confederacy | Statement: [Shawnee, formedConfederacyEfforts, Tecumseh’s confederacy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedConfederacyEfforts Context triple: [Shawnee, formedConfederacyEfforts, Tecumseh’s confederacy]
-
A.
confederateInitiative
Indicates that an entity initiates or undertakes an action in coordination or alliance with others as part of a confederate effort.
-
B.
joinedConfederateStatesOfAmerica
Indicates that an entity became a member of, or formally aligned itself with, the Confederate States of America.
-
C.
positionWithinConfederacy
Indicates that one entity holds a specific role, rank, or status within a confederated group or alliance of entities.
-
D.
formerConfederation
Indicates that an entity was previously part of a confederation but is no longer a member.
-
E.
formedConfederation
chosen
Indicates that two or more entities joined together to create a confederation, establishing a formal union or alliance among them.
- 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_69f76e5044248190b390d8887dc03254 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a009f53a4948190aef4ede1713e1748 |
completed | May 10, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_6a009edc53d4819080b22c1074a990f3 |
completed | May 10, 2026, 3:06 p.m. |
Created at: May 3, 2026, 4:09 p.m.