Triple
T36791865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Letter to Maris the Persian |
E909074
|
entity |
| Predicate | readAtCouncil |
P186301
|
FINISHED |
| Object | Council of Chalcedon |
—
|
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 Chalcedon | Statement: [Letter to Maris the Persian, readAtCouncil, Council of Chalcedon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: readAtCouncil Context triple: [Letter to Maris the Persian, readAtCouncil, Council of Chalcedon]
-
A.
heldCouncil
Indicates that an entity organized and conducted a formal meeting or assembly for discussion or decision-making with other participants.
-
B.
definedAtCouncil
Indicates that something was formally established, decided, or codified during a council or official deliberative meeting.
-
C.
council
Indicates that an entity serves as a governing or advisory council for another entity or within a particular domain.
-
D.
councilCan
Indicates that a council has the authority or permission to perform a specified action or exercise a particular power.
-
E.
councilConvokedBy
Indicates that a council or formal assembly was called together or convened by a particular person, group, or authority.
- F. None of above. chosen
Provenance (4 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_69f76e7a937c81909ed7359641e670f6 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7cabdd2d88190be1c8de7e499cb83 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c89b528c8190bf80b230fc7c7108 |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7ca91f1808190b2a05c4b691da0bb |
completed | May 3, 2026, 10:22 p.m. |
Created at: May 3, 2026, 4:12 p.m.