Triple
T4795297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of State (British India) |
E106695
|
entity |
| Predicate | legislativeHouse |
P12532
|
FINISHED |
| Object | upper house |
—
|
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: upper house | Statement: [Council of State (British India), legislativeHouse, upper house]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legislativeHouse Context triple: [Council of State (British India), legislativeHouse, upper house]
-
A.
parliamentaryHouse
chosen
Indicates that one entity functions as a parliamentary chamber or house within the legislative system of another entity.
-
B.
legislature
Indicates that an entity serves as, or is part of, a law-making body or assembly responsible for creating or amending laws for a political unit.
-
C.
lowerHouseOf
Indicates that one entity is the lower chamber in the bicameral legislature of another governing body or jurisdiction.
-
D.
legislativeChamberLevel
Indicates the hierarchical level (e.g., national, state, local) at which a legislative chamber operates within a political or governmental system.
-
E.
hasLegislatureType
Indicates the specific form or system of legislature that an entity possesses or operates under.
- 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_69bd43f591c881909e5a532388b0f3f3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6b40c29c8190adab3503f8ba0145 |
completed | March 20, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69bd622f88188190a51d52ccfad3d2dd |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:22 p.m.