Triple
T18269998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dick Act |
E437580
|
entity |
| Predicate | hasLegalCitationType |
P4979
|
FINISHED |
| Object | public 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: public law | Statement: [Dick Act, hasLegalCitationType, public law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegalCitationType Context triple: [Dick Act, hasLegalCitationType, public law]
-
A.
legalCitationType
chosen
Indicates the specific kind or category of legal citation that characterizes the relationship between the citing and cited legal sources.
-
B.
legalCitation
Indicates that one legal document, case, or authority formally references or cites another as a source of legal support or precedent.
-
C.
legalCitationSystem
Indicates a system or convention used to reference and identify legal authorities such as cases, statutes, or regulations.
-
D.
legalCitationNumber
Indicates the specific identifying number assigned to a legal citation that references a law, case, or legal document.
-
E.
hasLegalSystemType
Indicates that an entity possesses or is governed by a particular type or form of legal system.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ff7d4f88819084123ed6c9e7e5b8 |
completed | April 19, 2026, 4:14 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.