Triple
T31498896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tipra |
E803620
|
entity |
| Predicate | demographicMinorityInState |
P51820
|
FINISHED |
| Object | Tripura |
—
|
NE NERFINISHED |
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: Tripura | Statement: [Tipra, demographicMinorityInState, Tripura]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demographicMinorityInState Context triple: [Tipra, demographicMinorityInState, Tripura]
-
A.
hasMinorityIn
Indicates that one entity holds a non-controlling, minority ownership or stake in another entity.
-
B.
hasMinorityInHouse
Indicates that a political party or group holds fewer seats than any other in a legislative house, making it the smallest (minority) faction there.
-
C.
minorityMajority
chosen
Indicates that one group constitutes a numerical or power minority within a context while another group constitutes the corresponding majority.
-
D.
shareMinorityPopulations
Indicates that two entities have overlapping or similar minority population groups in terms of presence, composition, or distribution.
-
E.
demographicMajority
Indicates that one group constitutes more than half of the population within a specified context or area.
- 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_69f348cae52081909fa8e5f697523ae3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 9:43 p.m.