Triple
T36275455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | hwyfar |
E892793
|
entity |
| Predicate | notableOccurrenceIn |
—
|
GENERATED |
| Object | Arthurian legend via Gwenhwyfar |
—
|
UNRECOGNIZED GENERATED |
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableOccurrenceIn Context triple: [hwyfar, notableOccurrenceIn, Arthurian legend via Gwenhwyfar]
-
A.
notableEventMentionedIn
chosen
Indicates that a particular notable event is referenced or discussed within a specified source or document.
-
B.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
C.
notableActivityIn
Indicates that an entity is particularly recognized for performing a significant activity within a specified place, context, or domain.
-
D.
notableEventIncluded
Indicates that a particular notable event is contained within, or forms part of, a larger collection, record, or context.
-
E.
notableEventResponse
Indicates a response, reaction, or consequence that occurs as a result of a notable event.
- 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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.