Triple
T12974412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Sverre |
E321483
|
entity |
| Predicate | notableLawReform |
P61708
|
FINISHED |
| Object | Magnus VI’s law codification |
—
|
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: Magnus VI’s law codification | Statement: [House of Sverre, notableLawReform, Magnus VI’s law codification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLawReform Context triple: [House of Sverre, notableLawReform, Magnus VI’s law codification]
-
A.
notableReform
Indicates that an entity is recognized for having initiated, led, or been central to a significant reform or transformative change in a system, policy, or institution.
-
B.
associatedWithLegalReforms
chosen
Indicates a relationship where an entity is connected to, involved in, or influenced by specific legal reforms or changes in law.
-
C.
notableAreaOfLaw
Indicates that a person or entity is particularly recognized or distinguished in a specific field or area of law.
-
D.
legalReformer
Indicates that an entity works to change, improve, or modernize laws or legal systems.
-
E.
notableLegalWork
Indicates that an entity is recognized for significant contributions, cases, or achievements within the field of law.
- 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_69d80763bd6c819094437da5b20b01d2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97f2a71a0819098bb6cf8a4b2208a |
completed | April 10, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69d97dbdd94c8190ac4bbecca02dc77b |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:37 p.m.