Triple
T31936955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thessalian myth cycle |
E815416
|
entity |
| Predicate | hasMythicPlace |
P65692
|
FINISHED |
| Object | Iolcus |
—
|
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: Iolcus | Statement: [Thessalian myth cycle, hasMythicPlace, Iolcus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMythicPlace Context triple: [Thessalian myth cycle, hasMythicPlace, Iolcus]
-
A.
hasMythicSetting
chosen
Indicates that something is set within a mythic, legendary, or folklore-based world or context.
-
B.
hasMythicMotif
Indicates that one entity features, embodies, or is associated with a particular mythic motif found in the other entity.
-
C.
hasMythicalFigure
Indicates that one entity is associated with, features, or includes a particular mythical or legendary figure.
-
D.
hasMythicFounder
Indicates that an entity is traditionally believed to have been founded or established by a legendary or mythological figure rather than a historically verified person.
-
E.
hasMythicEvent
Indicates that an entity is associated with, involves, or features a significant mythic or legendary event.
- 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_69f348f3035c81908558e2339955abb3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:05 a.m.