Triple
T30107950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ε 201 |
E765181
|
entity |
| Predicate | overwrittenTextAuthor |
P85104
|
FINISHED |
| Object | Ephraem the Syrian |
—
|
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: Ephraem the Syrian | Statement: [ε 201, overwrittenTextAuthor, Ephraem the Syrian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overwrittenTextAuthor Context triple: [ε 201, overwrittenTextAuthor, Ephraem the Syrian]
-
A.
replacedDocumentAuthor
Indicates that one author of a document has been superseded or substituted by another author for that document.
-
B.
adaptedAuthor
Indicates that one entity is the author whose work has been adapted by another entity (e.g., into a different medium or format).
-
C.
palimpsestOvertextAuthor
chosen
Indicates that an author is responsible for writing the overlying (later) text layer in a palimpsest.
-
D.
composerOfTextSetting
Indicates that one entity is the composer who created the musical setting for a text associated with another entity.
-
E.
originAuthor
Indicates that an entity is the original creator or author of another entity (such as a work, document, or idea).
- 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67dbc4278819088f599a06c490287 |
completed | May 2, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:09 p.m.