Triple
T8262069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article IV territorial court |
E193216
|
entity |
| Predicate | hasJudgeTenure |
P73788
|
FINISHED |
| Object | fixed term |
—
|
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: fixed term | Statement: [Article IV territorial court, hasJudgeTenure, fixed term]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJudgeTenure Context triple: [Article IV territorial court, hasJudgeTenure, fixed term]
-
A.
hasLifeTenureJudges
Indicates that the judges associated with an office, position, or institution hold their roles for life, typically remaining in office until they choose to retire, resign, or are removed under exceptional circumstances.
-
B.
hasSeniorJudge
Indicates that one entity is assigned or linked to another entity serving in the role of a senior judge.
-
C.
maximumAgeOfJudges
Indicates the highest allowable age that individuals may have in order to serve as judges.
-
D.
hasJudge
Indicates that a legal case, proceeding, or decision is presided over or decided by a particular judge.
-
E.
termLengthOfJustices
chosen
Indicates the duration of time that justices serve in their official positions.
- 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_69ca82e081d48190986beaa51f498ab9 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7938723081909379cf78a4449b80 |
completed | March 31, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69cb36b8707881909aca349230495a5a |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:49 p.m.