Triple
T11550496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dioscorus of Alexandria |
E273875
|
entity |
| Predicate | chargeOrAccusation |
P21461
|
FINISHED |
| Object | Accused of heresy at the Council of Chalcedon |
—
|
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: Accused of heresy at the Council of Chalcedon | Statement: [Dioscorus of Alexandria, chargeOrAccusation, Accused of heresy at the Council of Chalcedon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chargeOrAccusation Context triple: [Dioscorus of Alexandria, chargeOrAccusation, Accused of heresy at the Council of Chalcedon]
-
A.
accusationType
Indicates the specific category or nature of an accusation made by one party against another.
-
B.
accusedIn
chosen
Indicates that a person or entity is formally charged with wrongdoing in a particular case, proceeding, or context.
-
C.
accusedOf
Indicates that one entity has formally alleged or claimed that another entity committed a specific wrongdoing or offense.
-
D.
charge
Indicates that one entity formally accuses another of an offense or imposes a financial cost or obligation on them.
-
E.
accuserIn
Indicates that one entity is the party who brings a charge or accusation against another entity within a specific context or case.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88a83f1e88190aabf11a4c8a6c9e5 |
completed | April 10, 2026, 5:28 a.m. |
| PD | Predicate disambiguation | batch_69d8087e57b48190a4c253dc0210f9d4 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.