Triple
T28656955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P75 |
E725358
|
entity |
| Predicate | containsCanonicalWork |
P128604
|
FINISHED |
| Object | New Testament |
—
|
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: New Testament | Statement: [P75, containsCanonicalWork, New Testament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsCanonicalWork Context triple: [P75, containsCanonicalWork, New Testament]
-
A.
isCanonicalWorkIn
chosen
Indicates that a work is recognized as an official or authoritative entry within a specified collection, corpus, or canon.
-
B.
containsWorksFrom
Indicates that one entity includes or holds works that originate from or are created by another entity.
-
C.
hasReferenceWork
Indicates that one entity is associated with a reference work (such as a dictionary, encyclopedia, or manual) that provides authoritative information about it.
-
D.
isAWorkBy
Indicates that one entity is a creative work that has been produced or authored by another entity.
-
E.
originalWorkFrom
Indicates that something is derived, adapted, or based on an earlier original work created by another source.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
Created at: April 28, 2026, 4:55 a.m.