Triple
T895069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reverend John Hale |
E19325
|
entity |
| Predicate | characterArc |
P20798
|
FINISHED |
| Object | moves from certainty to doubt |
—
|
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: moves from certainty to doubt | Statement: [Reverend John Hale, characterArc, moves from certainty to doubt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterArc Context triple: [Reverend John Hale, characterArc, moves from certainty to doubt]
-
A.
character1
Indicates that the subject is identified as the first or primary character in a narrative or context.
-
B.
character2
Indicates that a second character entity is involved in the relationship or context defined by the predicate.
-
C.
characterIn
Indicates that an entity appears as a character within a specified work, story, or narrative.
-
D.
supportingCharacter
Indicates that one entity plays a secondary or assisting role in the story or context relative to another primary entity.
-
E.
characterRoleSwap
Indicates a relationship where two characters exchange or assume each other’s narrative roles or functions within a story or scenario.
- 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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad22b6fc819093e655c8ce1f738b |
completed | March 1, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69a4aa94f7c881908deeb62308942e19 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab4a38ec8190915916d80299ab55 |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:39 p.m.