Triple
T29893829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Court |
E759222
|
entity |
| Predicate | mayOverturn |
P139986
|
FINISHED |
| Object | decisions of regional courts |
—
|
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: decisions of regional courts | Statement: [Imperial Court, mayOverturn, decisions of regional courts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayOverturn Context triple: [Imperial Court, mayOverturn, decisions of regional courts]
-
A.
overturnedDecisionOf
Indicates that one decision reversed, nullified, or set aside a previous decision.
-
B.
overturnedLaw
Indicates that a previously established law has been invalidated or reversed, typically by a higher legal authority or court decision.
-
C.
wasOverturnedByCourt
Indicates that a prior decision, ruling, or judgment was reversed or nullified by a court.
-
D.
seeksToOverturn
Indicates an attempt or intention by one entity to reverse, nullify, or invalidate a decision, state, rule, or outcome established by another.
-
E.
mayReverse
chosen
Indicates that an action, process, or state can be undone or returned to a previous condition.
- 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67729a7ac8190b99cf3fcc0e2c60c |
completed | May 2, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:03 p.m.