Triple
T5663996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judicial Proceedings Committee |
E124810
|
entity |
| Predicate | typeOfLawAddressed |
P6527
|
FINISHED |
| Object | substantive 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: substantive law | Statement: [Judicial Proceedings Committee, typeOfLawAddressed, substantive law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfLawAddressed Context triple: [Judicial Proceedings Committee, typeOfLawAddressed, substantive law]
-
A.
typeOfLaw
chosen
Indicates that one entity is a specific category or kind of law to which the other entity pertains.
-
B.
branchOfLaw
Indicates a relationship where one legal field or discipline is a subdivision or specialized area within a broader body of law.
-
C.
legalRepresentation
Indicates that one entity formally acts on behalf of another in legal matters, such as providing counsel, advocacy, or defense within a legal system.
-
D.
legalCase
Indicates a relationship where a formal legal dispute or proceeding exists between parties, typically adjudicated by a court or similar authority.
-
E.
litigationType
Indicates the specific category or nature of a legal dispute or court case associated with an entity or event.
- 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_69c00828906881908966f270b8f130cf |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0236d3f94819095111c41a323612d |
completed | March 22, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_69c021ba4ec481909db8cdbf0e907dd6 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:43 p.m.