Triple
T11008027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anna |
E260170
|
entity |
| Predicate | testimonyType |
P7873
|
FINISHED |
| Object | verbal proclamation about Jesus |
—
|
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: verbal proclamation about Jesus | Statement: [Anna, testimonyType, verbal proclamation about Jesus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testimonyType Context triple: [Anna, testimonyType, verbal proclamation about Jesus]
-
A.
gaveTestimonyIn
Indicates that one entity provided formal testimony or a statement in an official proceeding, event, or context associated with another entity.
-
B.
testimonyAffects
Indicates that one party’s testimony has an influence or impact on another entity, situation, or outcome.
-
C.
hasTestimony
chosen
Indicates that an entity provides, contains, or is associated with a formal statement or account (testimony) about another entity or event.
-
D.
viewOnTestimony
Indicates a stance or evaluation someone holds regarding the credibility, role, or use of testimony as a source of knowledge or evidence.
-
E.
savedByTestimonyOf
Indicates that an entity is rescued, delivered, or brought to salvation as a result of another entity’s testimony or witness.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79757bdcc8190900b267826eece21 |
completed | April 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d72e96be6c8190a46c69f61b2d8cd4 |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.