Triple
T12104188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Κάνωπος |
E288260
|
entity |
| Predicate | hasGreekMythologyConnection |
P9595
|
FINISHED |
| Object | Ναυτικός Κάνωπος της Τροίας |
—
|
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: Ναυτικός Κάνωπος της Τροίας | Statement: [Κάνωπος, hasGreekMythologyConnection, Ναυτικός Κάνωπος της Τροίας]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGreekMythologyConnection Context triple: [Κάνωπος, hasGreekMythologyConnection, Ναυτικός Κάνωπος της Τροίας]
-
A.
linkedToMythology
chosen
Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
-
B.
hasMythologicalNamesake
Indicates that one entity is named after, or shares its name with, a figure or element from mythology.
-
C.
hasMythologicalFeature
Indicates that an entity possesses a characteristic, attribute, or element derived from mythology or mythological beings.
-
D.
languageOfMyths
Indicates that the subject is the language in which the myths associated with the object are told or recorded.
-
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.
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_69d6ab4a5c448190a110d1273314b21a |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9164ada5081908676bd9e5947268a |
completed | April 10, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69d9150497408190921334d21503375a |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:48 p.m.