Triple
T29323300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rajouri Garden Assembly constituency |
E743570
|
entity |
| Predicate | hasVoterEligibilityAge |
P1871
|
FINISHED |
| Object | 18 years |
—
|
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: 18 years | Statement: [Rajouri Garden Assembly constituency, hasVoterEligibilityAge, 18 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVoterEligibilityAge Context triple: [Rajouri Garden Assembly constituency, hasVoterEligibilityAge, 18 years]
-
A.
voterEligibilityCriterion
Indicates the rule or condition that determines whether an individual is allowed to vote in a given context.
-
B.
governsAgeEligibility
Indicates that one entity sets or controls the age-related criteria determining another entity’s eligibility for something.
-
C.
votingAge
chosen
Indicates the minimum age at which an individual is legally permitted to vote.
-
D.
canVoteIn
Indicates that one entity has the legal right or eligibility to participate as a voter in an election or decision-making process associated with another entity.
-
E.
hasVotingAgePopulation
Indicates that an entity has a specified number or set of people who are of legal voting age within its population.
- 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 28, 2026, 1:24 p.m.