Triple
T14695774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Kekionga |
E345151
|
entity |
| Predicate | nativeAlliance |
P115387
|
FINISHED |
| Object | multi-tribal Native American 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: multi-tribal Native American confederacy | Statement: [Battle of Kekionga, nativeAlliance, multi-tribal Native American confederacy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nativeAlliance Context triple: [Battle of Kekionga, nativeAlliance, multi-tribal Native American confederacy]
-
A.
allianceBrandOf
Indicates a relationship where one brand is part of, or operates under, a broader alliance or group brand.
-
B.
recognizedAlliance
Indicates that one party formally acknowledges the existence and validity of an alliance involving another party.
-
C.
allianceType
Indicates the specific kind or category of alliance relationship that exists between entities.
-
D.
allianceDesignation
Indicates a formal relationship in which one entity designates or classifies another as an ally within an alliance.
-
E.
notNativeTo
Indicates that an entity does not originate from, or is not naturally occurring in, a specified place or environment.
- 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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb58855e081908b38f9515db5677f |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de657c57ec8190ae0b9bb79a514566 |
completed | April 14, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69de716d3aac8190aaa6dc1f099b86e8 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:28 a.m.