Triple
T9409244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scriptures (2 Peter 3:15–16) |
E226663
|
entity |
| Predicate | treatedOnParWith |
P89010
|
FINISHED |
| Object | other biblical texts |
—
|
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: other biblical texts | Statement: [Scriptures (2 Peter 3:15–16), treatedOnParWith, other biblical texts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatedOnParWith Context triple: [Scriptures (2 Peter 3:15–16), treatedOnParWith, other biblical texts]
-
A.
replacedAtPar
Indicates that one entity has been replaced by another at a specific location or position within a larger structure or sequence.
-
B.
parityWith
Indicates that two entities share the same parity, such as both being even or both being odd.
-
C.
hasPar
Indicates a relationship where one entity has another entity as its parent.
-
D.
arePartyTo
Indicates that the entities are participants or signatories in the same agreement, contract, or legal arrangement.
-
E.
operatedOn
Indicates that one entity has performed a surgical or procedural operation on 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_69ca843280488190bc65600e843ef9e6 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd52547f0c81908ed4f53b9f05ebaa |
completed | April 1, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69cca54c37f88190bddccf28e5fe5c84 |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca9d07eb08190866eb15333386dfa |
completed | April 1, 2026, 5:14 a.m. |
Created at: March 30, 2026, 7:47 p.m.