Triple
T31654683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhiannon |
E807826
|
entity |
| Predicate | hasCulturalOriginIn |
P56388
|
FINISHED |
| Object | Celtic mythology |
—
|
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: Celtic mythology | Statement: [Rhiannon, hasCulturalOriginIn, Celtic mythology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCulturalOriginIn Context triple: [Rhiannon, hasCulturalOriginIn, Celtic mythology]
-
A.
hasCulturalRoots
Indicates that something originates from, is shaped by, or is deeply connected to particular cultural traditions, practices, or heritage.
-
B.
hasCulturalPresenceOf
Indicates that something exhibits, contains, or is characterized by the cultural influence, activities, or representation of a particular group, tradition, or culture.
-
C.
cultureOfOrigin
chosen
Indicates the cultural background or tradition from which an entity originates or is derived.
-
D.
hasEthnicOrRegionalOrigin
Indicates that an entity originates from, or is associated with, a particular ethnic group or geographic region.
-
E.
hasAssociatedCulture
Indicates that an entity is related to, influenced by, or characterized by a particular culture.
- 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: April 30, 2026, 10:54 p.m.