Triple
T2480622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reichskammergericht |
E55805
|
entity |
| Predicate | adjudicated |
P19254
|
FINISHED |
| Object | major legal disputes |
—
|
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: major legal disputes | Statement: [Reichskammergericht, adjudicated, major legal disputes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjudicated Context triple: [Reichskammergericht, adjudicated, major legal disputes]
-
A.
canAdjudicate
chosen
Indicates that an entity has the authority or capacity to formally judge, decide, or resolve a dispute, case, or issue involving another entity or matter.
-
B.
adopted
Indicates that one entity has legally taken another (often a child or animal) into its family or care as a permanent member.
-
C.
settled
Indicates that an entity established residence or a stable presence in a place, typically after moving from elsewhere.
-
D.
decidedIn
Indicates that a decision, ruling, or outcome was made within a particular case, proceeding, or deliberative context.
-
E.
concluded
Indicates that an entity has brought an event, process, discussion, or agreement to an end, often after reaching a decision or final judgment.
- 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_69ab49e670a88190b928e08302381710 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd1eb3be481908fa7c6b8f1c78209 |
completed | March 7, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69abd0b5e3d481909a5cbc4a96edd24f |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:45 p.m.