Triple
T32547942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Against the Galileans |
E831894
|
entity |
| Predicate | hasResponseFrom |
P130112
|
FINISHED |
| Object | Cyril of Alexandria |
E19095
|
NE 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: Cyril of Alexandria | Statement: [Against the Galileans, hasResponseFrom, Cyril of Alexandria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResponseFrom Context triple: [Against the Galileans, hasResponseFrom, Cyril of Alexandria]
-
A.
hasResponseLine
Indicates that one entity includes, specifies, or is associated with a particular line of response provided by another entity or system.
-
B.
hasResponseMode
Indicates that an entity operates or behaves according to a particular mode or style of responding.
-
C.
hasResponderMessageCount
Indicates the number of messages sent by the responder in a given interaction or conversation.
-
D.
hasResponseAuthor
chosen
Indicates that a given response is authored or created by a specific agent or entity.
-
E.
hasAnswer
Indicates that one entity provides or contains a response or solution to a question, problem, or request associated with another entity.
- F. None of above.
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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a02fcbe03d0819082d3dd715ed41623 |
completed | May 12, 2026, 10:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3485ff77648190b1c9c2668b8d3c06 |
completed | June 18, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_6a02fc62138081908d2dbc5db7541d13 |
completed | May 12, 2026, 10:09 a.m. |
Created at: May 1, 2026, 1:02 a.m.