Triple
T19768884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Severo-Evensk |
E474827
|
entity |
| Predicate | indigenousPeopleInRegion |
P52996
|
FINISHED |
| Object | Even people |
—
|
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: Even people | Statement: [Severo-Evensk, indigenousPeopleInRegion, Even people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indigenousPeopleInRegion Context triple: [Severo-Evensk, indigenousPeopleInRegion, Even people]
-
A.
metIndigenousPeople
Indicates that an entity has encountered or come into contact with Indigenous people.
-
B.
primaryIndigenousGroups
chosen
Indicates the main Indigenous peoples or communities that are historically or predominantly associated with a particular place, group, or context.
-
C.
recognizedAsIndigenousPeopleBy
Indicates that one party formally acknowledges and accepts another party as belonging to an indigenous people or community.
-
D.
broaderIndigenousGrouping
Indicates that one indigenous group is a broader, more inclusive grouping that encompasses another, more specific indigenous group.
-
E.
refersToIndigenousPeopleOf
Indicates that one entity is about, concerns, or designates the indigenous people associated with another entity.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65359bb9881908f48282b63a83f2f |
completed | April 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:48 p.m.