Triple
T6267436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harmodius |
E140447
|
entity |
| Predicate | mythologizedAs |
P54696
|
FINISHED |
| Object | founder-hero of Athenian freedom |
—
|
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: founder-hero of Athenian freedom | Statement: [Harmodius, mythologizedAs, founder-hero of Athenian freedom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mythologizedAs Context triple: [Harmodius, mythologizedAs, founder-hero of Athenian freedom]
-
A.
mythologized
chosen
Indicates that one entity has been turned into or treated as a mythic, legendary, or highly idealized figure or story by another.
-
B.
mythologicalRole
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
C.
linkedToMythology
Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
-
D.
mythologicalCategory
Indicates that one entity is classified as belonging to the mythological type, group, or category represented by the other entity.
-
E.
eraOfMyth
Indicates a temporal relationship where an event, story, or phenomenon belongs to or takes place during a mythological or legendary era.
- 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_69c008cabc4081909723e2547c9d6cc0 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063a0f2548190a2f5c307bc5a67cf |
completed | March 22, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69c05606fb50819082d1a5a91e5030b6 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:25 p.m.