Triple
T30360210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hethum II of Armenia |
E772260
|
entity |
| Predicate | perpetratorOfAssassination |
P108209
|
FINISHED |
| Object | Mamluk agents |
—
|
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: Mamluk agents | Statement: [Hethum II of Armenia, perpetratorOfAssassination, Mamluk agents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perpetratorOfAssassination Context triple: [Hethum II of Armenia, perpetratorOfAssassination, Mamluk agents]
-
A.
wasAssassinatedIn
Indicates that an entity was killed in a deliberate, targeted assassination that occurred at a specific place or time.
-
B.
assassinationOrganizedBy
chosen
Indicates that an assassination was planned, directed, or coordinated by a particular agent or organization.
-
C.
wasAssassinationTarget
Indicates that an entity was the intended victim or objective of an assassination attempt.
-
D.
assassinatedIn
Indicates that an assassination of one entity occurred within the specified location or context represented by another entity.
-
E.
assassinationEvent
Indicates a deliberate killing of a specific individual, typically for political or strategic reasons, carried out as a planned event.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f682423e748190b20a754a0f1a9114 |
completed | May 2, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:57 p.m.