Triple
T27752415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andhra Pradesh Reorganisation Act, 2014 |
E701245
|
entity |
| Predicate | passedInLokSabhaOn |
P98495
|
FINISHED |
| Object | 2014-02-18 |
—
|
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: 2014-02-18 | Statement: [Andhra Pradesh Reorganisation Act, 2014, passedInLokSabhaOn, 2014-02-18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passedInLokSabhaOn Context triple: [Andhra Pradesh Reorganisation Act, 2014, passedInLokSabhaOn, 2014-02-18]
-
A.
datePassedInLokSabha
chosen
Indicates that a proposed bill or measure has been approved and passed by the Lok Sabha (the lower house of India’s Parliament).
-
B.
passedLegislation
Indicates that a governing body has formally approved and enacted a specific piece of legislation or law.
-
C.
passedChamber
Indicates that a proposed measure or bill has been approved by a specific legislative chamber.
-
D.
passedHouseVote
Indicates that a proposed measure or bill has received sufficient affirmative votes to be approved by the House of Representatives.
-
E.
chairedInLokSabhaBy
Indicates that a given session, meeting, or proceeding in the Lok Sabha was presided over or chaired by a specified individual.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 4:21 p.m.