Triple
T21008052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucknow West |
E517465
|
entity |
| Predicate | isSingleMemberConstituency |
P64717
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lucknow West, isSingleMemberConstituency, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSingleMemberConstituency Context triple: [Lucknow West, isSingleMemberConstituency, true]
-
A.
isNonMultiMemberDistrict
chosen
Indicates that an electoral district is represented by only a single member rather than multiple members.
-
B.
isOneOfAssemblyConstituenciesOf
Indicates that a given constituency is a member of, or belongs to, a specified set of assembly constituencies.
-
C.
isOneOfLargestConstituenciesBy
Indicates that an entity ranks among the largest constituencies when measured or determined according to a specified criterion or agent.
-
D.
isBoroughConstituency
Indicates that a parliamentary or electoral constituency is classified specifically as a borough constituency, as opposed to other constituency types.
-
E.
constituencyType
Indicates the specific kind or category of electoral or representative district to which an entity belongs or refers.
- 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_69e0b50192308190a284fcc89dd23a49 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc3dcb5081909b06d6db10fefba6 |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:53 p.m.