Triple
T429468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article I of the United States Constitution |
E9681
|
entity |
| Predicate | requiresMinimumAge |
P1130
|
FINISHED |
| Object | 25 years for Representatives |
—
|
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: 25 years for Representatives | Statement: [Article I of the United States Constitution, requiresMinimumAge, 25 years for Representatives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresMinimumAge Context triple: [Article I of the United States Constitution, requiresMinimumAge, 25 years for Representatives]
-
A.
hasLowerAge
Indicates that one entity is younger in age than another entity.
-
B.
militaryAge
Indicates that an entity is within the age range typically considered eligible for military service.
-
C.
hasAge
Indicates that an entity possesses a specific age value, typically expressed as a number of time units since its birth or creation.
-
D.
mandatoryRetirementAge
Indicates the age at which an individual is required by rule or policy to retire from a position or role.
-
E.
eligibilityCriteria
chosen
Indicates the conditions or requirements that must be satisfied for an entity to qualify for or be considered eligible 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_69a2e801e1d48190b505d1dd336b52ac |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eeedf68c81908473d6c6600961bd |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd7a3608190b8785c7b7205f6c1 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.