Triple
T449007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isis |
E7084
|
entity |
| Predicate | cultSuppressedBy |
P10731
|
FINISHED |
| Object | Christian Roman emperors |
—
|
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: Christian Roman emperors | Statement: [Isis, cultSuppressedBy, Christian Roman emperors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cultSuppressedBy Context triple: [Isis, cultSuppressedBy, Christian Roman emperors]
-
A.
suppressedDuring
chosen
Indicates that one event, action, or state is actively prevented, inhibited, or held back while another specified event, condition, or time period is occurring.
-
B.
consideredHeresyBy
Indicates that a belief, practice, or doctrine is judged to be heretical by a particular authority, group, or tradition.
-
C.
persecutedDuring
Indicates that one entity systematically harassed, oppressed, or victimized another entity during a specified time period or event.
-
D.
methodOfPersecution
Indicates the specific means, technique, or process by which an act of persecution is carried out.
-
E.
condemnedBy
Indicates that an entity is judged, denounced, or declared wrong or unacceptable 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_69a2e7e4676c81909ea0dbdecac0687c |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef6755a08190a057e72279b70456 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2ede1a1108190a4a06b3416ae6156 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.