Triple
T21887295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anand Lok Sabha constituency |
E540438
|
entity |
| Predicate | isPartOfNationalLegislature |
P146058
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Anand Lok Sabha constituency, isPartOfNationalLegislature, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfNationalLegislature Context triple: [Anand Lok Sabha constituency, isPartOfNationalLegislature, Yes]
-
A.
isPartOfStateLegislature
Indicates that an entity serves as a member or component within a specific state-level legislative body.
-
B.
isLegislativeBody
Indicates that the subject entity functions as an official law-making or legislative body within a political or organizational system.
-
C.
hasLegislatureType
Indicates the specific form or system of legislature that an entity possesses or operates under.
-
D.
hasAssociatedLegislature
Indicates that an entity is linked to a specific legislative body that holds authority or responsibility over it.
-
E.
legislativeBodyMemberOf
Indicates that an individual serves as a member of a specified legislative body or assembly.
- 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_69e0c47a95908190ae3e19b716accb3d |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118ed35948190bbffba2c40029eee |
completed | April 28, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6d054737081908aa7112975b77475 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 7:05 p.m.