Triple
T20735719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Frazee |
E509697
|
entity |
| Predicate | assertedSincerityOfBelief |
P141310
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [William Frazee, assertedSincerityOfBelief, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assertedSincerityOfBelief Context triple: [William Frazee, assertedSincerityOfBelief, yes]
-
A.
invokesBeliefIn
Indicates that one entity causes, triggers, or calls upon a belief or mental acceptance of something in another entity.
-
B.
maintainsBeliefDespite
Indicates that an entity continues to hold a particular belief even in the face of opposing evidence, pressure, or changing circumstances.
-
C.
requiresBeliefIn
Indicates that one entity can only be valid, accessible, or fulfilled if belief in another specified entity or proposition is held.
-
D.
believedTo
Indicates that one entity holds a belief or conviction about the truth, existence, or properties of another entity or proposition.
-
E.
believedBy
Indicates that a particular proposition, statement, or entity is held to be true or accepted as real by a specified believer.
- F. None of above. chosen
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_69e0b4c589c08190834fb5d86d0efa2b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c20a02d48190bba22d1bdbeb370d |
completed | April 21, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3cbe5788190b7ace43bfdac2ef6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:31 p.m.