Triple
T34865426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1972 Burundian genocide |
E1004994
|
entity |
| Predicate | targetedGroupCharacteristic |
P65675
|
FINISHED |
| Object | ethnicity |
—
|
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: ethnicity | Statement: [1972 Burundian genocide, targetedGroupCharacteristic, ethnicity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetedGroupCharacteristic Context triple: [1972 Burundian genocide, targetedGroupCharacteristic, ethnicity]
-
A.
groupCharacterization
chosen
Indicates how a group as a whole is described or characterized in terms of its shared properties, traits, or defining features.
-
B.
membershipCharacteristic
Indicates that an entity possesses a specific attribute or quality by virtue of its membership in a particular group or category.
-
C.
entityCharacteristic
Indicates that an entity possesses, exhibits, or is defined by a particular characteristic or attribute.
-
D.
hasNotableGroupCharacteristic
Indicates that a group possesses a distinctive or noteworthy characteristic that sets it apart from other groups.
-
E.
subjectHasCharacteristic
Indicates that a subject possesses, exhibits, or is defined by a particular characteristic or attribute.
- 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fec25f0fc48190b87ab1f9cd1eb0de |
completed | May 9, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69fec079a770819098df7cc3049df954 |
completed | May 9, 2026, 5:04 a.m. |
Created at: May 3, 2026, 4 p.m.