Triple
T756449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mapp v. Ohio |
E15566
|
entity |
| Predicate | relatedAreaOfLaw |
P2167
|
FINISHED |
| Object | United States 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: United States constitutional law | Statement: [Mapp v. Ohio, relatedAreaOfLaw, United States constitutional law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedAreaOfLaw Context triple: [Mapp v. Ohio, relatedAreaOfLaw, United States constitutional law]
-
A.
relatedLegalSystem
Indicates that there is an association or connection between two legal systems, such as influence, similarity, shared origin, or mutual relevance.
-
B.
branchOfLaw
Indicates a relationship where one legal field or discipline is a subdivision or specialized area within a broader body of law.
-
C.
legalArea
chosen
Indicates the specific field or branch of law that a legal matter, case, or document pertains to.
-
D.
laterLegalJurisdiction
Indicates that one legal jurisdiction succeeds or replaces another jurisdiction at a later point in time.
-
E.
legalJurisdiction
Indicates the legal authority or geographic area whose laws and courts have the power to govern, regulate, or adjudicate matters involving the related entities.
- 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_69a493599a0081908da65f3407af1ef2 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a66ab4608190afcd81e6606c5116 |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a50348088190873a1446db657a78 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.