Triple
T34958041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haakonian Order |
E1008171
|
entity |
| Predicate | committedAtrocity |
P167962
|
FINISHED |
| Object | annihilation of Rinax |
—
|
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: annihilation of Rinax | Statement: [Haakonian Order, committedAtrocity, annihilation of Rinax]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: committedAtrocity Context triple: [Haakonian Order, committedAtrocity, annihilation of Rinax]
-
A.
commitsMassacreAt
Indicates that an entity carries out a large-scale, deliberate killing of many people at a specified location or event.
-
B.
committedCrime
Indicates that an entity has carried out or been responsible for a criminal act or offense.
-
C.
commitsCrimeIn
Indicates that an entity carries out or is responsible for a criminal act within a specified location or jurisdiction.
-
D.
associatedWithCrimesAgainstHumanity
Indicates a relationship in which an entity is linked or connected to the planning, commission, support, or responsibility for crimes against humanity.
-
E.
perpetratorOfCrimeAgainst
chosen
Indicates that one entity is the person or group responsible for committing a crime against 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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4 p.m.