Triple
T30645341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lay magistrates |
E780103
|
entity |
| Predicate | upperAgeLimitForAppointment |
P30982
|
FINISHED |
| Object | 65 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: 65 years | Statement: [Lay magistrates, upperAgeLimitForAppointment, 65 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upperAgeLimitForAppointment Context triple: [Lay magistrates, upperAgeLimitForAppointment, 65 years]
-
A.
maximumAgeRequirement
chosen
Indicates that there is an upper age limit that an entity must not exceed in order for a condition, participation, or eligibility to apply.
-
B.
maximumRegistrationAge
Indicates the highest age at which an entity is allowed or eligible to register.
-
C.
mayBeReappointedUntilAge
Indicates that an individual is allowed to be reappointed to a position repeatedly up to, but not beyond, a specified age limit.
-
D.
cardinalElectorUpperAgeLimit
Indicates the maximum age at which a person is eligible to serve as a cardinal elector.
-
E.
governsAgeEligibility
Indicates that one entity sets or controls the age-related criteria determining another entity’s eligibility for something.
- 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_69f224a50ebc81909b961a94c7f66b12 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:29 p.m.