Triple
T20133926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Lerna |
E490969
|
entity |
| Predicate | associatedMythType |
P54299
|
FINISHED |
| Object | heroic exploit |
—
|
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: heroic exploit | Statement: [Lake Lerna, associatedMythType, heroic exploit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedMythType Context triple: [Lake Lerna, associatedMythType, heroic exploit]
-
A.
linkedToMythology
Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
-
B.
mythologicalCategory
chosen
Indicates that one entity is classified as belonging to the mythological type, group, or category represented by the other entity.
-
C.
sharesMythosWith
Indicates that two entities are associated with, or originate from, the same mythological tradition, narrative system, or shared set of myths.
-
D.
mythologicalContent
Indicates that the subject contains, references, or is associated with myths, mythological narratives, or myth-based elements.
-
E.
mythologicalRole
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
- 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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6676556c481909ffc80cd2009b65a |
completed | April 20, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:32 p.m.