Triple
T24785331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agnes Nutter |
E620101
|
entity |
| Predicate | prophecyStyle |
P59950
|
FINISHED |
| Object | comically specific |
—
|
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: comically specific | Statement: [Agnes Nutter, prophecyStyle, comically specific]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prophecyStyle Context triple: [Agnes Nutter, prophecyStyle, comically specific]
-
A.
prophecyTheme
Indicates that the relationship or action centers on the theme, content, or subject matter of a prophecy.
-
B.
prophecyMade
Indicates that a prophetic statement or prediction has been declared by one entity concerning a future event or outcome involving another entity.
-
C.
typeOfProphecy
chosen
Indicates the specific category or kind of prophecy that a given prophetic statement or vision belongs to.
-
D.
prophecyContent
Indicates that the object expresses the specific message, information, or details contained within a prophecy.
-
E.
prophecyTradition
Indicates a relationship where a prophetic message, practice, or belief is transmitted, preserved, or interpreted within a particular religious or cultural tradition.
- 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:45 a.m.