Triple
T36339499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Algerian Civil Concord policy |
E894873
|
entity |
| Predicate | excludedCrimes |
P185141
|
FINISHED |
| Object | mass killings |
—
|
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: mass killings | Statement: [Algerian Civil Concord policy, excludedCrimes, mass killings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: excludedCrimes Context triple: [Algerian Civil Concord policy, excludedCrimes, mass killings]
-
A.
crimeType
Indicates the specific category or nature of the crime associated with an event or entity.
-
B.
includesCrimesAgainstSociety
Indicates that the referenced entity involves, encompasses, or is associated with offenses classified as crimes against society (such as public order, moral, or regulatory violations).
-
C.
crimeAdditionalAct
Indicates that an additional criminal act is associated with, or occurs in conjunction with, a primary crime.
-
D.
committedCrime
Indicates that an entity has carried out or been responsible for a criminal act or offense.
-
E.
excludedFromAmnesty
Indicates that an entity is not eligible for, or is specifically denied, the benefits or protections granted by an amnesty.
- F. None of above. chosen
Provenance (4 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_69f76e4e90148190b02fe52593c70b5b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7bb3ff1b08190802b1063d55d3923 |
completed | May 3, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a611a081908dd6aec1df3f4d7f |
completed | May 3, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69f7bb3f23f48190b0b9c2d667e09b52 |
completed | May 3, 2026, 9:16 p.m. |
Created at: May 3, 2026, 4:09 p.m.