Triple
T32896520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanda, Rampur |
E841488
|
entity |
| Predicate | hasUpperLegislature |
P42195
|
FINISHED |
| Object | Parliament of India |
—
|
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: Parliament of India | Statement: [Tanda, Rampur, hasUpperLegislature, Parliament of India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUpperLegislature Context triple: [Tanda, Rampur, hasUpperLegislature, Parliament of India]
-
A.
hasUpperHouseCountry
Indicates that a country possesses an upper house within its national legislative or parliamentary system.
-
B.
hasLegislatureType
Indicates the specific form or system of legislature that an entity possesses or operates under.
-
C.
haveUpperHouseRepresentationIn
chosen
Indicates that an entity holds or is assigned representation in a specified upper legislative chamber.
-
D.
hasLegislativePower
Indicates that an entity possesses the authority to create, amend, or repeal laws within a given jurisdiction or governing framework.
-
E.
hasHigherLegislativeDistrict
Indicates that one legislative district is hierarchically above or encompasses another legislative district within a legislative system.
- 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:18 a.m.