Triple
T4736394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phaethon |
E105135
|
entity |
| Predicate | settingOfMyth |
P58483
|
FINISHED |
| Object | sky |
—
|
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: sky | Statement: [Phaethon, settingOfMyth, sky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingOfMyth Context triple: [Phaethon, settingOfMyth, sky]
-
A.
mythologicalRole
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
B.
eraOfMyth
Indicates a temporal relationship where an event, story, or phenomenon belongs to or takes place during a mythological or legendary era.
-
C.
expandsMythologyOf
Indicates that one entity broadens, enriches, or adds new elements to the mythological background or lore associated with another entity.
-
D.
mythologicalEvent
Indicates an event or occurrence that takes place within mythological narratives or traditions, often involving gods, heroes, or supernatural phenomena.
-
E.
mythologicalCategory
Indicates that one entity is classified as belonging to the mythological type, group, or category represented by the other entity.
- F. None of above. chosen
Provenance (4 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_69bd43ee52048190b81a4f066534ffb3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64831c58819098758ac1f7839b3a |
completed | March 20, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69bd6221c3b881908604f35f8de6f16b |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd637e19e081909e415544106c7835 |
completed | March 20, 2026, 3:10 p.m. |
Created at: March 20, 2026, 1:19 p.m.