Triple
T34231060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eimer |
E878193
|
entity |
| Predicate | hasMythologicalRootsIn |
P126681
|
FINISHED |
| Object | Irish 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: Irish mythology | Statement: [Eimer, hasMythologicalRootsIn, Irish mythology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMythologicalRootsIn Context triple: [Eimer, hasMythologicalRootsIn, Irish mythology]
-
A.
hasMythologicalBasis
chosen
Indicates that something is founded on, derived from, or significantly influenced by a mythological story, figure, or tradition.
-
B.
hasMythologicalUsage
Indicates that something is used, referenced, or functions within a mythological context or tradition.
-
C.
hasMythologicalNamesake
Indicates that one entity is named after, or shares its name with, a figure or element from mythology.
-
D.
hasMythologicalInhabitant
Indicates that a place or location is traditionally believed to be inhabited or occupied by a mythological being or creature.
-
E.
hasMythologicalFeature
Indicates that an entity possesses a characteristic, attribute, or element derived from mythology or mythological beings.
- 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_69f349b16d0481908754e3069f05e0c1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:56 a.m.