Triple
T776237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potawatomi |
E16391
|
entity |
| Predicate | historicallyAlliedWith |
P19658
|
FINISHED |
| Object | French colonists |
—
|
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: French colonists | Statement: [Potawatomi, historicallyAlliedWith, French colonists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyAlliedWith Context triple: [Potawatomi, historicallyAlliedWith, French colonists]
-
A.
alliesInWar
Indicates that two or more parties are cooperating as allies on the same side in a specific war or armed conflict.
-
B.
countryOnAlliedSide
Indicates that a country is aligned with and actively supports a particular side or coalition in a conflict, alliance, or broader geopolitical context.
-
C.
mainAlliedPower
Indicates that an entity serves as a primary or leading ally to another entity within an alliance or coalition.
-
D.
isNATOAllyOf
Indicates that one entity is a member of NATO and has a formal alliance relationship with the other entity within the NATO framework.
-
E.
notableAlliedNation
Indicates that one nation is prominently recognized as an ally or key partner of another nation.
- F. None of above. chosen
Provenance (4 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_69a49369a0848190af883934cee3db4c |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a74da7648190adfad56717d564df |
completed | March 1, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69a4a50a443481909ae3662764ee69a4 |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a74c81bc81909f4ac9c1677b09c2 |
completed | March 1, 2026, 8:53 p.m. |
Created at: March 1, 2026, 7:37 p.m.