Triple
T899489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titus |
E19414
|
entity |
| Predicate | testifiesTo |
P18400
|
FINISHED |
| Object | grace of God |
—
|
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: grace of God | Statement: [Titus, testifiesTo, grace of God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testifiesTo Context triple: [Titus, testifiesTo, grace of God]
-
A.
hasTestimony
Indicates that an entity provides, contains, or is associated with a formal statement or account (testimony) about another entity or event.
-
B.
gaveTestimonyIn
Indicates that one entity provided formal testimony or a statement in an official proceeding, event, or context associated with another entity.
-
C.
attestedBy
chosen
Indicates that the existence, occurrence, or validity of something is supported, confirmed, or documented by a specified source or authority.
-
D.
testament
Indicates a formal declaration or document that expresses and legally records a person’s intentions, often regarding property or beliefs, typically to take effect after their death.
-
E.
demonstratedBy
Indicates that something is shown, proven, or made evident through the actions, behavior, or example of 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_69a4939e889c8190ac148b3ac1a7f90b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad4162848190aa2787b2fa3e6575 |
completed | March 1, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69a4aa979d408190b17ccfde132ea628 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.