Triple
T30745211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gospel of John chapter 10 |
E782797
|
entity |
| Predicate | traditionalAuthorOfBook |
P58465
|
FINISHED |
| Object | John the Apostle |
—
|
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: John the Apostle | Statement: [Gospel of John chapter 10, traditionalAuthorOfBook, John the Apostle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalAuthorOfBook Context triple: [Gospel of John chapter 10, traditionalAuthorOfBook, John the Apostle]
-
A.
traditionalAuthor
Indicates that an entity is regarded as the conventional or historically accepted author of a work, even if actual authorship may be uncertain or disputed.
-
B.
favoriteAuthor
Indicates that one entity is the author whom another entity prefers above all others.
-
C.
authorTraditionallyAscribedTo
chosen
Indicates that authorship of a work is customarily or historically attributed to an entity, even if definitive proof of authorship may be uncertain or disputed.
-
D.
canonicalAuthor
Indicates that an entity is the officially recognized or standard author of a given work or resource.
-
E.
wasWrittenBy
Indicates that a text, document, or work is authored or created by a particular entity.
- 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe00dad1708190b6522476bebb43af |
completed | May 8, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69fdfc3717f48190bb50ac2919c8ef95 |
completed | May 8, 2026, 3:07 p.m. |
Created at: April 29, 2026, 8:38 p.m.