Triple
T20832942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Les Boréades |
E512876
|
entity |
| Predicate | settingMythology |
P105028
|
FINISHED |
| Object | Greek 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: Greek mythology | Statement: [Les Boréades, settingMythology, Greek mythology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingMythology Context triple: [Les Boréades, settingMythology, Greek mythology]
-
A.
settingOfMyth
Indicates that a location or environment serves as the backdrop or context in which a particular myth takes place.
-
B.
mythologicalContent
Indicates that the subject contains, references, or is associated with myths, mythological narratives, or myth-based elements.
-
C.
subsequentMythology
Indicates that one mythology develops later than, or is derived from, another mythology in time or tradition.
-
D.
mythologicalCategory
Indicates that one entity is classified as belonging to the mythological type, group, or category represented by the other entity.
-
E.
mythologicalSetting
chosen
Indicates that an entity is set within, associated with, or takes place in 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_69e0b4cf62a88190bbf92351e9e57259 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c3235a7c8190a00dbd7008cf107a |
completed | April 21, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a1f4f48190aa9fb4ef8f8aea5a |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:42 p.m.