Triple
T30107888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Codex Ephraemi Rescriptus |
E765180
|
entity |
| Predicate | overwrittenBy |
P168457
|
FINISHED |
| Object | writings of Ephraem the Syrian |
—
|
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: writings of Ephraem the Syrian | Statement: [Codex Ephraemi Rescriptus, overwrittenBy, writings of Ephraem the Syrian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overwrittenBy Context triple: [Codex Ephraemi Rescriptus, overwrittenBy, writings of Ephraem the Syrian]
-
A.
overshadowedBy
Indicates that one entity’s importance, visibility, or impact is diminished because another entity is more prominent or dominant.
-
B.
overrides
Indicates that one entity replaces, supersedes, or takes precedence over another in determining the outcome or applicable behavior.
-
C.
wasSupersededBy
Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
-
D.
overriddenInPartBy
Indicates that one item’s provisions or effects are partially superseded or modified by another item.
-
E.
overarchedBy
Indicates that one entity is physically or conceptually spanned, covered, or dominated from above by another entity.
- F. None of above. chosen
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_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_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 7:09 p.m.