Triple
T26006455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Martyr Kyriaki |
E646772
|
entity |
| Predicate | sufferedUnder |
P48045
|
FINISHED |
| Object | Roman Empire |
—
|
NE NERFINISHED |
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: Roman Empire | Statement: [Holy Martyr Kyriaki, sufferedUnder, Roman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sufferedUnder Context triple: [Holy Martyr Kyriaki, sufferedUnder, Roman Empire]
-
A.
sufferedCondition
Indicates that an entity experienced or was afflicted by a particular condition, typically adverse or harmful, at some point in time.
-
B.
regardsSufferingAs
Indicates how an entity perceives, evaluates, or emotionally responds to the suffering of another entity.
-
C.
resultOfTorture
Indicates that something occurs as a direct consequence or outcome of an act of torture.
-
D.
wasPersecutedBy
chosen
Indicates that an entity was subjected to persistent hostility, oppression, or harmful treatment carried out by another entity.
-
E.
sufferedOccupationBy
Indicates that an entity experienced harm, hardship, or adverse conditions as a result of being occupied or controlled by another entity.
- 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6057a92fc81908a29ab4a8ff9f7d8 |
completed | May 2, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69f4a10728e08190bc0b96c558740f51 |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 9 a.m.