Triple
T31045926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muscogee people |
E791125
|
entity |
| Predicate | formedConfederacy |
P117976
|
FINISHED |
| Object | Muscogee 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: Muscogee Confederacy | Statement: [Muscogee people, formedConfederacy, Muscogee Confederacy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedConfederacy Context triple: [Muscogee people, formedConfederacy, Muscogee 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.
positionWithinConfederacy
Indicates that one entity holds a specific role, rank, or status within a confederated group or alliance of entities.
-
D.
formedConfederation
chosen
Indicates that two or more entities joined together to create a confederation, establishing a formal union or alliance among them.
-
E.
traditionalConfederationUnit
Indicates a relationship where an entity is a traditional or historically recognized sub-unit within a larger confederation or federated structure.
- 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff1c91bbac8190b84012dee1cb3b2c |
completed | May 9, 2026, 11:37 a.m. |
| PD | Predicate disambiguation | batch_69ff1c23ca508190bb5a435d765b7e53 |
completed | May 9, 2026, 11:36 a.m. |
Created at: April 29, 2026, 8:59 p.m.