Triple
T16948547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ptolemy son of Abubus |
E411125
|
entity |
| Predicate | timeOfAssassinationOfSimonThassi |
P4179
|
FINISHED |
| Object | c. 134 BCE |
—
|
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: c. 134 BCE | Statement: [Ptolemy son of Abubus, timeOfAssassinationOfSimonThassi, c. 134 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfAssassinationOfSimonThassi Context triple: [Ptolemy son of Abubus, timeOfAssassinationOfSimonThassi, c. 134 BCE]
-
A.
assassinationDate
chosen
Indicates the date on which an assassination of the referenced entity occurred.
-
B.
assassinationEvent
Indicates a deliberate killing of a specific individual, typically for political or strategic reasons, carried out as a planned event.
-
C.
assassinatedIn
Indicates that an assassination of one entity occurred within the specified location or context represented by another entity.
-
D.
relatedAssassination
Indicates a relationship where one entity is connected to, involved in, or associated with an assassination event concerning another entity.
-
E.
assassinationAttemptLocation
Indicates the place where an attempted assassination occurred or was intended to occur.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cfb4b1b08190b608d36a209ed6bd |
completed | April 18, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.