Triple
T8446343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myrddin Wyllt |
E199685
|
entity |
| Predicate | propheticRole |
P59231
|
FINISHED |
| Object | foretells future events |
—
|
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: foretells future events | Statement: [Myrddin Wyllt, propheticRole, foretells future events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propheticRole Context triple: [Myrddin Wyllt, propheticRole, foretells future events]
-
A.
propheticActivity
chosen
Indicates engaging in or being associated with acts of prophecy, such as receiving, delivering, or performing messages believed to be divinely inspired.
-
B.
symbolicRoleInProphecy
Indicates that an entity serves as a symbolic figure or sign within a prophecy, representing or foreshadowing specific events, themes, or outcomes.
-
C.
subjectOfProphecy
Indicates that the subject is foretold or predicted to play a significant role or experience a specific event according to a prophecy.
-
D.
prophecyKnownAs
Indicates that a particular prophecy is referred to or recognized by a specific name or title.
-
E.
prophecyHeardBy
Indicates that a prophecy was heard or received by a particular entity.
- 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_69ca83170f9081909cd98f55614c6476 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe3152a3c819092efdeab718def7a |
completed | March 31, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69cbd0f5a3648190beb53a139a2d5482 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:09 p.m.