Triple
T1315781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamburg massacre |
E28098
|
entity |
| Predicate | hasLegalOutcome |
P2931
|
FINISHED |
| Object | no white perpetrators convicted |
—
|
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: no white perpetrators convicted | Statement: [Hamburg massacre, hasLegalOutcome, no white perpetrators convicted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegalOutcome Context triple: [Hamburg massacre, hasLegalOutcome, no white perpetrators convicted]
-
A.
legalOutcome
chosen
Indicates the resulting legal status, decision, or consequence that follows from a legal process, action, or judgment.
-
B.
hasLegalProceeding
Indicates that there is a formal legal action, case, or proceeding involving the related entities.
-
C.
hasLegalIssue
Indicates that an entity is involved in, associated with, or subject to a legal problem, dispute, or proceeding.
-
D.
hasLegalStatus
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
-
E.
hasLegalRight
Indicates that an entity possesses an officially recognized legal entitlement or permission to perform an action or hold a claim regarding another entity.
- 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_69a498532c3481909223b74af2e578df |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c173a72481909a820d6da6ef9e69 |
completed | March 1, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69a4beebcb348190964bd7215811942c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.