Triple
T1419396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Watchtower |
E31988
|
entity |
| Predicate | doctrinalFocus |
P15112
|
FINISHED |
| Object | Bible prophecy |
—
|
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: Bible prophecy | Statement: [The Watchtower, doctrinalFocus, Bible prophecy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doctrinalFocus Context triple: [The Watchtower, doctrinalFocus, Bible prophecy]
-
A.
doctrinalEmphasis
chosen
Indicates a relationship where a doctrine, belief system, or teaching is given particular focus, priority, or stress within a religious, ideological, or organizational context.
-
B.
theologicalFocus
Indicates that something is primarily concerned with, centered on, or directed toward theological themes, questions, or doctrines.
-
C.
doctrinalStance
Indicates the specific set of doctrines, beliefs, or official teachings that an entity adheres to or promotes.
-
D.
doctrinalStatus
Indicates the formal standing or classification of a belief, teaching, or doctrine within a particular religious or ideological system.
-
E.
doctrinalOutcome
Indicates the result or consequence that follows from applying or adopting a particular doctrine, teaching, or set of beliefs.
- 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_69a49919a994819086528951bc224775 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c40631e881909ddf81a2eb84af1c |
completed | March 1, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69a4bf060b0081909ba00e6ac093a28b |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.