Triple
T9966031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geoffrey of Monmouth (literary consolidation) |
E195685
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | literary phenomenon |
C524
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: literary phenomenon Context triple: [Geoffrey of Monmouth (literary consolidation), instanceOf, literary phenomenon]
-
A.
cultural phenomenon
chosen
A cultural phenomenon is a widely recognized pattern of behavior, belief, or expression that emerges within a society and significantly influences its values, practices, or identity.
-
B.
literary landmark
A literary landmark is a historically or culturally significant location, object, or work that has had a lasting impact on literature, its development, or its readership.
-
C.
literary celebration
A literary celebration is an event or occasion dedicated to honoring, enjoying, and promoting literature, its creators, and its cultural impact through activities such as readings, discussions, and performances.
-
D.
fictional phenomenon
A fictional phenomenon is an imagined event, process, or occurrence that exists only within the context of a narrative or invented world, governed by that setting’s own internal logic rather than real-world science.
-
E.
literary genre
A literary genre is a category of written works defined by shared stylistic, thematic, or structural characteristics that shape readers’ expectations and interpretations.
- F. None of above.
Provenance (1 batch)
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_69ca82ebd1288190912f9e4482d1fa35 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 8:47 p.m.