Triple
T24221023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wordarrows |
E601455
|
entity |
| Predicate | creatorTribalAffiliation |
P147216
|
FINISHED |
| Object | Anishinaabe |
—
|
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: Anishinaabe | Statement: [Wordarrows, creatorTribalAffiliation, Anishinaabe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creatorTribalAffiliation Context triple: [Wordarrows, creatorTribalAffiliation, Anishinaabe]
-
A.
creatorEthnicGroup
chosen
Indicates that an entity was created by a person or group belonging to a specified ethnic group.
-
B.
tribeOrGens
Indicates a relationship where an entity belongs to, is associated with, or is identified as a particular tribe or gens (clan/lineage group).
-
C.
tribeProgenitorOf
Indicates that one entity is the original ancestor or founding progenitor from which a particular tribe or tribal group descends.
-
D.
hasTribalAssociation
Indicates that an entity is affiliated with, belongs to, or is formally associated with a particular tribe or tribal group.
-
E.
ethnicOrTribalBase
Indicates that something is founded on, derived from, or primarily organized around a particular ethnic or tribal group or identity.
- 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_69e29537ca548190b94a37ebe1977caf |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f287d9cb4481909a77616dc123d16b |
completed | April 29, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:59 p.m.