Triple
T5220461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rehnquist Court |
E117854
|
entity |
| Predicate | notableAreaOfLaw |
P62104
|
FINISHED |
| Object | constitutional law |
—
|
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: constitutional law | Statement: [Rehnquist Court, notableAreaOfLaw, constitutional law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAreaOfLaw Context triple: [Rehnquist Court, notableAreaOfLaw, constitutional law]
-
A.
branchOfLaw
Indicates a relationship where one legal field or discipline is a subdivision or specialized area within a broader body of law.
-
B.
notableLegalCode
Indicates that a legal code is especially significant, influential, or noteworthy in relation to the referenced entity.
-
C.
notableLegalWork
Indicates that an entity is recognized for significant contributions, cases, or achievements within the field of law.
-
D.
notableOfficeJurisdiction
Indicates that a person’s notable office or position is associated with authority or responsibility over a specific jurisdiction or geographic area.
-
E.
lawJournal
Indicates a relationship where a work is published in, associated with, or appears within a specific law journal.
- F. None of above. chosen
Provenance (4 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_69bd4465e03081909bfcfd7113062590 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7ab846548190bcd2c5cd238f6cd9 |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77bd2a448190a9ae5afd2585a7b9 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd78a89b608190b259d3d8658f8f7c |
completed | March 20, 2026, 4:41 p.m. |
Created at: March 20, 2026, 1:48 p.m.