Triple
T32108550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Algapur |
E820052
|
entity |
| Predicate | hasUpperHouseCountry |
P173806
|
FINISHED |
| Object | Rajya 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: Rajya Sabha | Statement: [Algapur, hasUpperHouseCountry, Rajya Sabha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUpperHouseCountry Context triple: [Algapur, hasUpperHouseCountry, Rajya Sabha]
-
A.
haveUpperHouseRepresentationIn
Indicates that an entity holds or is assigned representation in a specified upper legislative chamber.
-
B.
upperHouseInvolved
Indicates that the upper legislative chamber (e.g., senate) participates in, influences, or is formally involved in the referenced action, process, or decision.
-
C.
upperHouseCounterpart
Indicates that one legislative body is the corresponding or equivalent chamber in the upper house relative to another body.
-
D.
upperHouseStatus
Indicates the status or role an entity holds within an upper legislative chamber (such as membership, position, or standing).
-
E.
hasLowerHouseSeats
Indicates the number of seats an entity holds in the lower house of a bicameral legislature.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ba1733408190af579d93a7946508 |
completed | May 3, 2026, 2:59 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:27 a.m.