Triple
T4734656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pokagon Band of Potawatomi Indians |
E105093
|
entity |
| Predicate | hasCommunityFocus |
P43777
|
FINISHED |
| Object | cultural continuity |
—
|
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: cultural continuity | Statement: [Pokagon Band of Potawatomi Indians, hasCommunityFocus, cultural continuity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommunityFocus Context triple: [Pokagon Band of Potawatomi Indians, hasCommunityFocus, cultural continuity]
-
A.
focusesOnCommunity
chosen
Indicates that the subject prioritizes and directs attention or effort toward the well-being, needs, or development of a community.
-
B.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
C.
hasCommunityArea
Indicates that an entity is associated with, located in, or belongs to a particular community area.
-
D.
hasMajorCommunity
Indicates that an entity possesses a primary or significantly large community associated with it.
-
E.
includesCommunity
Indicates that one entity encompasses, contains, or has within it a particular community as part of its scope or composition.
- 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_69bd43ee52048190b81a4f066534ffb3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6467a1fc819089485b4d76e0edc4 |
completed | March 20, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69bd6221c3b881908604f35f8de6f16b |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:19 p.m.