Triple
T9215560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erasmus’s Greek New Testament editions |
E221232
|
entity |
| Predicate | laterIncludes |
P56452
|
FINISHED |
| Object | 1 John 5:7 Comma Johanneum under pressure |
—
|
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: 1 John 5:7 Comma Johanneum under pressure | Statement: [Erasmus’s Greek New Testament editions, laterIncludes, 1 John 5:7 Comma Johanneum under pressure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterIncludes Context triple: [Erasmus’s Greek New Testament editions, laterIncludes, 1 John 5:7 Comma Johanneum under pressure]
-
A.
laterIncludedOn
chosen
Indicates that one entity was added to, incorporated into, or featured on another entity at a subsequent time.
-
B.
laterComplementedBy
Indicates that an earlier entity is subsequently supplemented, enhanced, or completed by a later entity.
-
C.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
D.
laterIn
Indicates that one event, state, or time point occurs after another in temporal order.
-
E.
laterFeature
Indicates that one feature, event, or element occurs or is introduced after another in time.
- 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_69ca83eae42c8190a0ea9e040710a277 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccda0830a8819096a186ed2e976cba |
completed | April 1, 2026, 8:40 a.m. |
| PD | Predicate disambiguation | batch_69cc660ce23c81909c7bbe10f4a05f36 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:27 p.m.