Triple
T33324114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | well-maiden |
E853218
|
entity |
| Predicate | foundInMythology |
P9595
|
FINISHED |
| Object | Celtic mythology |
—
|
NE NERFINISHED |
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: [well-maiden, foundInMythology, Celtic mythology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundInMythology Context triple: [well-maiden, foundInMythology, Celtic mythology]
-
A.
linkedToMythology
chosen
Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
-
B.
mythologicalCategory
Indicates that one entity is classified as belonging to the mythological type, group, or category represented by the other entity.
-
C.
mythologicalTextMention
Indicates that a mythological text mentions, references, or otherwise explicitly refers to a given entity or concept.
-
D.
mythologicalContent
Indicates that the subject contains, references, or is associated with myths, mythological narratives, or myth-based elements.
-
E.
hasMythologicalInhabitant
Indicates that a place or location is traditionally believed to be inhabited or occupied by a mythological being or creature.
- 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe7bfc94bc81909eeec946e8c1c450 |
completed | May 9, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69fe7b74a1188190886f128e07f712da |
completed | May 9, 2026, 12:10 a.m. |
Created at: May 1, 2026, 1:33 a.m.