Triple
T5467029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ceryneian Hind |
E122735
|
entity |
| Predicate | belongsToMythology |
P9595
|
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: [Ceryneian Hind, belongsToMythology, Greek mythology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToMythology Context triple: [Ceryneian Hind, belongsToMythology, Greek mythology]
-
A.
linkedToMythology
chosen
Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
-
B.
mythologicalCategory
Indicates that one entity is classified as belonging to the mythological type, group, or category represented by the other entity.
-
C.
mythologicalRole
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
D.
expandsMythologyOf
Indicates that one entity broadens, enriches, or adds new elements to the mythological background or lore associated with another entity.
-
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_69bd4643f16081908d7f29e08096115a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927c946c8190aef40679199fede3 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a370a88190b5d17b8a5387138d |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:08 p.m.