Triple
T25284924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nandurbar Lok Sabha constituency |
E633911
|
entity |
| Predicate | isTribalDominatedArea |
P87161
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Nandurbar Lok Sabha constituency, isTribalDominatedArea, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTribalDominatedArea Context triple: [Nandurbar Lok Sabha constituency, isTribalDominatedArea, true]
-
A.
hasNearbyTribalLand
Indicates that an entity is located close to or adjacent to land officially recognized as belonging to a tribal nation or indigenous community.
-
B.
hasTribalPresence
chosen
Indicates that a tribal group is present, active, or represented in relation to the referenced entity or location.
-
C.
hasTribalEntity
Indicates that one entity is associated with, belongs to, or is part of a specific tribal group or tribal organizational body.
-
D.
hasTribalCitizens
Indicates that one or more individuals are recognized as official members or citizens of a particular tribe.
-
E.
hasTribalHeadquartersNearby
Indicates that the subject entity is located close to the tribal headquarters of a Native nation or tribe.
- 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48e0800a881909bf6099d120338a5 |
completed | May 1, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:19 p.m.