Triple
T16885950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superior Court of New Jersey |
E421539
|
entity |
| Predicate | mandatoryRetirementAgeForJudges |
P2272
|
FINISHED |
| Object | 70 |
—
|
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: 70 | Statement: [Superior Court of New Jersey, mandatoryRetirementAgeForJudges, 70]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mandatoryRetirementAgeForJudges Context triple: [Superior Court of New Jersey, mandatoryRetirementAgeForJudges, 70]
-
A.
maximumAgeOfJudges
Indicates the highest allowable age that individuals may have in order to serve as judges.
-
B.
hasSeniorJudge
Indicates that one entity is assigned or linked to another entity serving in the role of a senior judge.
-
C.
minimumJurorAge
Indicates the minimum age requirement that an individual must meet to be eligible to serve as a juror.
-
D.
judgesServeUntil
Indicates that a judge continues to hold and perform their judicial office up to a specified end date or condition.
-
E.
mandatoryRetirementAge
chosen
Indicates the age at which an individual is required by rule or policy to retire from a position or role.
- 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_69d889d470fc8190b4aec199636c0c56 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3bbc126e881909dae8133ad34acc9 |
completed | April 18, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69e32b90ec3c819099c51bb7baf2984c |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:29 a.m.