Triple
T26211050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Singhbhum region |
E655487
|
entity |
| Predicate | tribalPopulation |
P145707
|
FINISHED |
| Object | significant |
—
|
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: significant | Statement: [Singhbhum region, tribalPopulation, significant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tribalPopulation Context triple: [Singhbhum region, tribalPopulation, significant]
-
A.
ethnicGroupCountApprox
Indicates an approximate count of distinct ethnic groups associated with or present in a given entity.
-
B.
ethnicGroupSize
chosen
Indicates the number of individuals belonging to a particular ethnic group within a specified population or context.
-
C.
federallyRecognizedTribes
Indicates that the entities are Native American tribes that have been formally acknowledged and granted legal status by the federal government.
-
D.
numberOfTribes
Indicates the total count of distinct tribes associated with a given entity or context.
-
E.
federallyRecognizedTribe
Indicates that the subject is officially acknowledged by the federal government as a Native American tribe with a recognized government-to-government relationship.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60d1706d481908ca3c7c39ba0d157 |
completed | May 2, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:52 p.m.