Triple
T508367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Council of Constantinople |
E10550
|
entity |
| Predicate | addressed |
P1286
|
FINISHED |
| Object | writings of Theodore of Mopsuestia |
—
|
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: writings of Theodore of Mopsuestia | Statement: [Second Council of Constantinople, addressed, writings of Theodore of Mopsuestia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressed Context triple: [Second Council of Constantinople, addressed, writings of Theodore of Mopsuestia]
-
A.
addressesIssue
Indicates that one entity deals with, responds to, or attempts to resolve a specific issue associated with another entity.
-
B.
address
chosen
Indicates that one entity directs spoken or written communication specifically to another entity.
-
C.
considered
Indicates that one entity regards, judges, or thinks about another entity in a particular way or context.
-
D.
settled
Indicates that an entity established residence or a stable presence in a place, typically after moving from elsewhere.
-
E.
adopted
Indicates that one entity has legally taken another (often a child or animal) into its family or care as a permanent member.
- 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_69a2e848adf881908e5e04f7af030093 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f162f3888190b057ad04e40a30e2 |
completed | Feb. 28, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69a2edfe236481909901cc7d4281b33c |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.