Triple
T1784670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Title II – Public Accommodations |
E39363
|
entity |
| Predicate | primaryRemedy |
P2242
|
FINISHED |
| Object | injunctive relief |
—
|
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: injunctive relief | Statement: [Title II – Public Accommodations, primaryRemedy, injunctive relief]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRemedy Context triple: [Title II – Public Accommodations, primaryRemedy, injunctive relief]
-
A.
remedy
Indicates that one entity serves to cure, alleviate, or counteract a problem, illness, or undesirable condition affecting another entity.
-
B.
remedySought
chosen
Indicates that a particular legal or corrective action is being requested as a solution or relief in response to a problem or dispute.
-
C.
primaryFront
Indicates that one entity serves as the main or most important front-facing side or surface in relation to another entity.
-
D.
primaryService
Indicates that one entity serves as the main or principal service provided or used in relation to another entity.
-
E.
primaryCoverage
Indicates that one entity serves as the main or principal source of coverage (such as insurance or protection) for 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_69a88630519c8190a17addd83c4a3ef4 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab75457e54819096b8c6ae8c65550c |
completed | March 7, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69aa61d165688190924962a98e07ff69 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.