Triple
T887331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Low Christology |
E19158
|
entity |
| Predicate | inDialogueWith |
P12142
|
FINISHED |
| Object | High 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: High Christology | Statement: [Low Christology, inDialogueWith, High Christology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inDialogueWith Context triple: [Low Christology, inDialogueWith, High Christology]
-
A.
dialogueWith
chosen
Indicates that two entities are engaged in a mutual conversational exchange or dialogue with each other.
-
B.
isTalkingPicture
Indicates that the subject is a motion picture that includes synchronized recorded sound, especially spoken dialogue.
-
C.
alsoSpeak
Indicates that an entity, in addition to another language or mode of communication already mentioned, speaks this additional language or communicates in this additional way.
-
D.
roleInDialogue
Indicates that an entity participates in a dialogue with a specific conversational role (e.g., speaker, listener, moderator) relative to other participants.
-
E.
spokeAt
Indicates that a person delivered a talk, speech, or presentation at a particular event or location.
- 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_69a4939c32488190a7ccd41cf0abb22b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ae787bf081909533082ca013624a |
completed | March 1, 2026, 9:24 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8ff8c48190a33b00acf65c1276 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.