Triple
T32930459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | How Jesus Became God |
E842385
|
entity |
| Predicate | hasCompanionResponseBook |
P2758
|
FINISHED |
| Object | How God Became Jesus |
E842385
|
NE 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: How God Became Jesus | Statement: [How Jesus Became God, hasCompanionResponseBook, How God Became Jesus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompanionResponseBook Context triple: [How Jesus Became God, hasCompanionResponseBook, How God Became Jesus]
-
A.
hasCompanionBook
chosen
Indicates that one entity (typically a primary work) is associated with another entity that serves as its companion book, providing supplementary or related content.
-
B.
hasCompanionContent
Indicates that one piece of content is accompanied by related or supplementary content intended to be used or consumed together.
-
C.
hasCompanionDocument
Indicates that one document is associated with and serves as a companion to another document.
-
D.
companionBookCoAuthor
Indicates that an entity is a co-author of a companion book associated with another work or subject.
-
E.
hasBook
Indicates that an entity possesses, owns, or is associated with a particular book.
- F. None of above.
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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34d2642be88190b3834d23da8cd900 |
completed | June 19, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:20 a.m.