Triple
T19610311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minnesota Statutes |
E470711
|
entity |
| Predicate | legalHierarchyRole |
P6053
|
FINISHED |
| Object | codification of Minnesota session laws |
—
|
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: codification of Minnesota session laws | Statement: [Minnesota Statutes, legalHierarchyRole, codification of Minnesota session laws]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalHierarchyRole Context triple: [Minnesota Statutes, legalHierarchyRole, codification of Minnesota session laws]
-
A.
legalHierarchyRank
chosen
Indicates the relative position or level of authority an entity holds within a legal or judicial hierarchy.
-
B.
legalSystemRole
Indicates the specific function, capacity, or position an entity holds within a legal or judicial system.
-
C.
libraryRole
Indicates the specific function, responsibility, or position an entity holds within the context of a library.
-
D.
managementRole
Indicates that one entity holds a managerial or supervisory role with authority and responsibility over another entity.
-
E.
ordinationRole
Indicates the specific religious or ceremonial office, function, or capacity in which an entity is formally ordained.
- 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640cb180c8190ba96ffb69c24e2e1 |
completed | April 20, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69e514e166dc8190a0f147e0b4c8bbe7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.