Triple
T35811935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | სომხები |
E1035253
|
entity |
| Predicate | ისტორიული ტრავმა |
P98487
|
FINISHED |
| Object | სომხთა გენოციდი |
—
|
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: სომხთა გენოციდი | Statement: [სომხები, ისტორიული ტრავმა, სომხთა გენოციდი]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ისტორიული ტრავმა Context triple: [სომხები, ისტორიული ტრავმა, სომხთა გენოციდი]
-
A.
trauma
Indicates that an entity has experienced a deeply distressing or harmful event or series of events that cause lasting psychological or emotional impact.
-
B.
traumaTheme
chosen
Indicates that the relationship or context involves themes of trauma, such as psychological injury, distressing experiences, or their emotional and narrative impact.
-
C.
მემკვიდრეობა
Indicates the relationship in which rights, property, or status are passed from one party to another as an inheritance.
-
D.
hasTragicPast
Indicates that an entity has experienced a significantly sorrowful or traumatic history that influences its present state or characterization.
-
E.
traumaSource
Indicates that one entity is the origin or cause of another entity’s trauma.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:06 p.m.