Triple
T21728470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clytie Sutpen |
E536334
|
entity |
| Predicate | narrativeTrait |
P79666
|
FINISHED |
| Object | enigmatic |
—
|
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: enigmatic | Statement: [Clytie Sutpen, narrativeTrait, enigmatic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrativeTrait Context triple: [Clytie Sutpen, narrativeTrait, enigmatic]
-
A.
narrativeCharacteristic
chosen
Indicates that one entity serves as a descriptive or defining narrative feature or quality of another entity.
-
B.
narrative
Indicates that one entity tells, presents, or conveys a story or sequence of events about another entity or situation.
-
C.
narrativeType
Indicates the specific kind or category of narrative (e.g., genre, structural form, or storytelling mode) associated with an entity.
-
D.
narrativeCharacter
Indicates that one entity functions as a character within the narrative or story associated with another entity.
-
E.
narrativeTradition
Indicates the storytelling customs, conventions, or patterns that shape how narratives are typically told within a particular culture, group, or context.
- 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_69e0c46d3284819099a4f9d5a704eb95 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69effd03c6ec8190a2f0445c1f3a45b4 |
completed | April 28, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:48 p.m.