Triple
T37339979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christotokos |
E927005
|
entity |
| Predicate | wasOpposedAtCouncil |
P181334
|
FINISHED |
| Object | Council of Ephesus |
—
|
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: Council of Ephesus | Statement: [Christotokos, wasOpposedAtCouncil, Council of Ephesus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasOpposedAtCouncil Context triple: [Christotokos, wasOpposedAtCouncil, Council of Ephesus]
-
A.
triedAtCouncil
Indicates that an entity was subjected to a formal trial or judgment process conducted by a council or governing body.
-
B.
heldCouncil
Indicates that an entity organized and conducted a formal meeting or assembly for discussion or decision-making with other participants.
-
C.
opposedDuring
chosen
Indicates that one entity actively resisted or was in conflict with another entity during a specified time period or event.
-
D.
definedAtCouncil
Indicates that something was formally established, decided, or codified during a council or official deliberative meeting.
-
E.
councilCan
Indicates that a council has the authority or permission to perform a specified action or exercise a particular power.
- 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_69f76eb4e8a881908bd40da28f36fc7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8c38a9688190be524246f5682107 |
completed | May 6, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9c6e0481908565bd849e869b24 |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.