Triple
T33727140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Affirmation |
E864173
|
entity |
| Predicate | hasParatextualElement |
P44720
|
FINISHED |
| Object | fictional documents within the narrative |
—
|
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: fictional documents within the narrative | Statement: [The Affirmation, hasParatextualElement, fictional documents within the narrative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParatextualElement Context triple: [The Affirmation, hasParatextualElement, fictional documents within the narrative]
-
A.
hasProseElements
Indicates that something contains or is composed of prose components, such as sentences, paragraphs, or narrative text.
-
B.
includesParatext
chosen
Indicates that one entity contains or is accompanied by paratextual material (such as prefaces, notes, or other supplementary text) related to another entity.
-
C.
hasParagraph
Indicates that one entity contains or is associated with a specific paragraph as part of its content or structure.
-
D.
hasPar
Indicates a relationship where one entity has another entity as its parent.
-
E.
hasTextElement
Indicates that an entity contains or is associated with a specific text-based component or segment.
- 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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff53389a0481908b2baeb43c6294f0 |
completed | May 9, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69ff52e2b4b88190b38d160d771fe14b |
completed | May 9, 2026, 3:29 p.m. |
Created at: May 1, 2026, 1:44 a.m.