Triple
T13670153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ho-Chunk Nation of Wisconsin |
E327725
|
entity |
| Predicate | hasTribalSeal |
P111088
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ho-Chunk Nation of Wisconsin, hasTribalSeal, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTribalSeal Context triple: [Ho-Chunk Nation of Wisconsin, hasTribalSeal, yes]
-
A.
hasTribalPresence
Indicates that a tribal group is present, active, or represented in relation to the referenced entity or location.
-
B.
hasTribalAuthority
Indicates that an entity holds recognized governing or decision-making power within a specific tribe or tribal community.
-
C.
hasTribalAssociation
Indicates that an entity is affiliated with, belongs to, or is formally associated with a particular tribe or tribal group.
-
D.
hasRecognizedTribe
Indicates that an entity is officially acknowledged or designated as a tribe by a relevant authority or governing body.
-
E.
isSealOf
Indicates that one entity serves as the official seal, emblem, or stamp that authenticates, endorses, or formally represents another entity.
- 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc6599c248190b7f134b5b9947a23 |
completed | April 12, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8d8d0881908d6e89954f44eed4 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:53 p.m.