Triple
T31281731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reang tribe of Tripura |
E797687
|
entity |
| Predicate | stateListedAs |
P194083
|
FINISHED |
| Object | Scheduled Tribe in Tripura |
—
|
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: Scheduled Tribe in Tripura | Statement: [Reang tribe of Tripura, stateListedAs, Scheduled Tribe in Tripura]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateListedAs Context triple: [Reang tribe of Tripura, stateListedAs, Scheduled Tribe in Tripura]
-
A.
stateIncludes
Indicates that a given state encompasses, contains, or has within its boundaries another specified entity or region.
-
B.
statusInUnitedStates
Indicates the legal or official standing that an entity holds within the jurisdiction of the United States.
-
C.
statehoodStatus
Indicates the legal or political condition of an entity regarding whether, how, or to what extent it is recognized or functions as a state.
-
D.
stateCapitalStatus
Indicates that an entity serves as the official capital city of a specified state or state-level administrative region.
-
E.
stateName
Indicates that an entity is identified by or associated with a particular state’s name.
- F. None of above. chosen
Provenance (4 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_69f224def9088190a37034eab3daf57f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
| PDg | Predicate description generation | batch_69fd5f2903a48190ac4b718bff99c6cf |
completed | May 8, 2026, 3:57 a.m. |
Created at: April 29, 2026, 9:13 p.m.