Triple
T12618598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of Constantinople 867 |
E301319
|
entity |
| Predicate | deepened |
P11185
|
FINISHED |
| Object | rift between Byzantine and Roman churches |
—
|
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: rift between Byzantine and Roman churches | Statement: [Council of Constantinople 867, deepened, rift between Byzantine and Roman churches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deepened Context triple: [Council of Constantinople 867, deepened, rift between Byzantine and Roman churches]
-
A.
depth
Indicates the vertical distance from a reference surface or top point down to a lower point or bottom within a medium or space.
-
B.
tooDeepFor
Indicates that one entity’s depth exceeds the level at which another entity can effectively operate, reach, or function.
-
C.
delayed
Indicates that an expected event, action, or outcome occurred later than its scheduled or usual time.
-
D.
down
Indicates that one entity is located at a lower position or level relative to another entity or reference point.
-
E.
entrenched
chosen
Indicates that something is firmly and deeply established in a position, practice, or condition, making it difficult to change or remove.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b195108190ac25bd95e644ace4 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:13 p.m.