Triple
T36791866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Letter to Maris the Persian |
E909074
|
entity |
| Predicate | evaluatedByCouncil |
P7823
|
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, evaluatedByCouncil, Council of Chalcedon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evaluatedByCouncil Context triple: [Letter to Maris the Persian, evaluatedByCouncil, Council of Chalcedon]
-
A.
councilEvaluates
Indicates that a council assesses, reviews, or judges the qualities, performance, or suitability of a given entity or proposal.
-
B.
councilOutcome
Indicates the result or decision produced by a council after its deliberation or proceedings.
-
C.
councilCan
Indicates that a council has the authority or permission to perform a specified action or exercise a particular power.
-
D.
definedAtCouncil
chosen
Indicates that something was formally established, decided, or codified during a council or official deliberative meeting.
-
E.
council
Indicates that an entity serves as a governing or advisory council for another entity or within a particular domain.
- 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_69f76e7a937c81909ed7359641e670f6 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:12 p.m.