Triple
T7188903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of Chalcedon |
E167636
|
entity |
| Predicate | taughtAbout |
P21344
|
FINISHED |
| Object | Christology |
—
|
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: Christology | Statement: [Council of Chalcedon, taughtAbout, Christology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taughtAbout Context triple: [Council of Chalcedon, taughtAbout, Christology]
-
A.
teachesAbout
chosen
Indicates that one entity provides instruction or information to another entity on a particular subject or topic.
-
B.
taughtThat
Indicates that one entity provided instruction or education to another entity about a specific subject, skill, or concept.
-
C.
taughtAs
Indicates that one entity served as a teacher or instructor for another entity in an educational or training context.
-
D.
taughtThrough
Indicates that one entity provided instruction, education, or training to another entity by means of a specified method, medium, or intermediary.
-
E.
teachableFrom
Indicates that one entity can be taught or learned from another entity, capturing a directional teachability or learnability relationship between them.
- 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_69c6888b5248819090499a884ee3ec39 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e8e3d9188190ba2792098d76fb86 |
completed | March 27, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69c6e752385c819096fbab55566ee2a8 |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:50 p.m.