Triple
T285598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Testament manuscripts |
E5878
|
entity |
| Predicate | precede |
P97
|
FINISHED |
| Object | printed New Testament editions |
—
|
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: printed New Testament editions | Statement: [New Testament manuscripts, precede, printed New Testament editions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precede Context triple: [New Testament manuscripts, precede, printed New Testament editions]
-
A.
predecessor
chosen
Indicates that one entity comes before another in an ordered sequence or succession.
-
B.
precedentFor
Indicates that one situation, decision, or case serves as an authoritative example or basis for deciding or interpreting another.
-
C.
cededTo
Indicates that control, ownership, or authority over something was formally transferred from one entity to another.
-
D.
pretext
Indicates that one party uses a stated reason or excuse to conceal their true motive for an action or decision.
-
E.
anticipates
Indicates that one entity expects or predicts a future event, action, or state involving another entity before it actually occurs.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a2605b372c8190831570aa6532cc96 |
completed | Feb. 28, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69a25b7a8d148190aacdcc8ccb35c7f3 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.