Triple
T20171018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sahariya |
E491957
|
entity |
| Predicate | vulnerableGroupStatus |
P101412
|
FINISHED |
| Object | particularly vulnerable tribal group |
—
|
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: particularly vulnerable tribal group | Statement: [Sahariya, vulnerableGroupStatus, particularly vulnerable tribal group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vulnerableGroupStatus Context triple: [Sahariya, vulnerableGroupStatus, particularly vulnerable tribal group]
-
A.
ethnicGroupStatus
chosen
Indicates the social, legal, or political standing or classification of an ethnic group within a given context.
-
B.
hasVolunteerStatus
Indicates that an entity holds a particular volunteer-related status or role within a specified context.
-
C.
groupStatusIntroduced
Indicates that a group has been newly created or formally introduced into a system or context.
-
D.
hasPopulationStatus
Indicates the current demographic condition or classification of a population associated with an entity.
-
E.
vowStatus
Indicates the current state or condition of a commitment or promise made between entities, such as whether it is active, fulfilled, or broken.
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e66848ae3c8190aa5fde66da35a89a |
completed | April 20, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:35 p.m.