Triple
T23385280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pushyamitra Shunga |
E593859
|
entity |
| Predicate | allegedPersecutionOf |
P82697
|
FINISHED |
| Object | Buddhists |
—
|
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: Buddhists | Statement: [Pushyamitra Shunga, allegedPersecutionOf, Buddhists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedPersecutionOf Context triple: [Pushyamitra Shunga, allegedPersecutionOf, Buddhists]
-
A.
persecutionOf
chosen
Indicates the act of subjecting an entity to persistent, often unjust hostility, harassment, or oppression, typically on the basis of identity, beliefs, or group membership.
-
B.
persecutedIn
Indicates that an entity is subjected to oppression, harassment, or unfair treatment within a particular place, context, or time period.
-
C.
causeOfPersecution
Indicates that one entity is the reason or basis for another entity being persecuted.
-
D.
wasPersecutedBy
Indicates that an entity was subjected to persistent hostility, oppression, or harmful treatment carried out by another entity.
-
E.
persecutedDuring
Indicates that one entity systematically harassed, oppressed, or victimized another entity during a specified time period or 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_69e25d2754fc819085deea939bde60ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a497661c8190b52fa27419594989 |
completed | April 29, 2026, 6:26 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:35 p.m.