Triple
T34130869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Government in Jharkhand |
E875420
|
entity |
| Predicate | hasLowerHouseRepresentation |
P27960
|
FINISHED |
| Object | Lok Sabha |
—
|
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: Lok Sabha | Statement: [Central Government in Jharkhand, hasLowerHouseRepresentation, Lok Sabha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLowerHouseRepresentation Context triple: [Central Government in Jharkhand, hasLowerHouseRepresentation, Lok Sabha]
-
A.
haveUpperHouseRepresentationIn
Indicates that an entity holds or is assigned representation in a specified upper legislative chamber.
-
B.
hasHouseOfDeputiesRepresentation
chosen
Indicates that an entity is represented within a House of Deputies, such as by having delegates or deputies acting on its behalf.
-
C.
hasLowerHouseSeats
Indicates the number of seats an entity holds in the lower house of a bicameral legislature.
-
D.
hasLowerHouseCountry
Indicates that a lower legislative house is associated with or belongs to a particular country.
-
E.
hasSpeakerInLowerHouse
Indicates that an entity serves as the presiding officer (speaker) of a specified lower house in a bicameral legislature.
- 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_69f349aa33848190a2e6c5e4533c8444 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fecd0a732c819097bdd3eb69b6158c |
completed | May 9, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69fecc0318d481908b5b20598a76a9fe |
completed | May 9, 2026, 5:54 a.m. |
Created at: May 1, 2026, 1:53 a.m.