Triple
T27277192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lehri District |
E688225
|
entity |
| Predicate | hasTribalSociety |
P70068
|
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: [Lehri District, hasTribalSociety, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTribalSociety Context triple: [Lehri District, hasTribalSociety, true]
-
A.
hasTribalCommunities
chosen
Indicates that an entity possesses, includes, or is associated with one or more tribal communities.
-
B.
hasTribalInstitution
Indicates that an entity possesses, is associated with, or hosts a tribal institution (such as a tribal government, organization, or culturally recognized tribal body).
-
C.
hasTribalAssociation
Indicates that an entity is affiliated with, belongs to, or is formally associated with a particular tribe or tribal group.
-
D.
hasTribalCitizens
Indicates that one or more individuals are recognized as official members or citizens of a particular tribe.
-
E.
ethnicOrTribalBase
Indicates that something is founded on, derived from, or primarily organized around a particular ethnic or tribal group or identity.
- 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_69ef3558cf8881909595ef89daf6e14a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: April 27, 2026, 11:03 a.m.