Triple
T13786491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article I court |
E331270
|
entity |
| Predicate | judgeSalaryProtection |
P81557
|
FINISHED |
| Object | not constitutionally guaranteed |
—
|
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: not constitutionally guaranteed | Statement: [Article I court, judgeSalaryProtection, not constitutionally guaranteed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: judgeSalaryProtection Context triple: [Article I court, judgeSalaryProtection, not constitutionally guaranteed]
-
A.
hasJudgeSalaryProtection
chosen
Indicates that a judge’s salary is legally protected from reduction or interference while they hold judicial office.
-
B.
salaryProtection
Indicates that an arrangement exists to maintain or safeguard an individual's salary level against reduction under certain conditions.
-
C.
salary
Indicates the amount of monetary compensation an entity receives, typically on a regular basis, for work or services performed.
-
D.
payScale
Indicates the compensation level or salary range assigned to an entity, typically reflecting its relative pay or grade within a structured system.
-
E.
benefitProtection
Indicates that one entity provides protective advantages or safeguards that benefit another entity.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0249e4f88190a80316394940627d |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:11 p.m.