Triple
T10662834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vale of Tempe |
E251270
|
entity |
| Predicate | inMythology |
P9595
|
FINISHED |
| Object | place favored by Apollo |
—
|
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: place favored by Apollo | Statement: [Vale of Tempe, inMythology, place favored by Apollo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inMythology Context triple: [Vale of Tempe, inMythology, place favored by Apollo]
-
A.
mythologicalCategory
Indicates that one entity is classified as belonging to the mythological type, group, or category represented by the other entity.
-
B.
linkedToMythology
chosen
Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
-
C.
subsequentMythology
Indicates that one mythology develops later than, or is derived from, another mythology in time or tradition.
-
D.
mythologicalRole
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
E.
mythologicalFigureFeatured
Indicates that a mythological figure is prominently depicted, referenced, or plays a significant role within a given work, context, or medium.
- 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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6f31b72d081908ec8029cd9f6d814 |
completed | April 9, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8753108190b799ffa0c760526e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:08 p.m.