Triple
T30844010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beza’s Greek New Testament |
E785586
|
entity |
| Predicate | usesManuscript |
P48215
|
FINISHED |
| Object | Codex Bezae |
—
|
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: Codex Bezae | Statement: [Beza’s Greek New Testament, usesManuscript, Codex Bezae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesManuscript Context triple: [Beza’s Greek New Testament, usesManuscript, Codex Bezae]
-
A.
sendsManuscriptTo
Indicates that one entity transmits or delivers a manuscript to another entity as the intended recipient.
-
B.
areManuscriptsOf
Indicates that the subject entities are manuscripts that are versions, copies, or instances of the work represented by the object entity.
-
C.
hasManuscriptsIn
Indicates that an entity possesses or is associated with manuscripts that are located in a specified place or collection.
-
D.
associatedWithManuscript
chosen
Indicates a relationship in which an entity is linked or connected to a particular manuscript, such as by authorship, reference, inclusion, or relevance.
-
E.
usedInManuscripts
Indicates that something (such as a term, symbol, or feature) appears or is employed within one or more manuscripts.
- 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 29, 2026, 8:46 p.m.