Triple
T26076518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Athens (through the story of Theseus) |
E657699
|
entity |
| Predicate | mythicAlliance |
P162910
|
FINISHED |
| Object | Heracles |
—
|
NE NERFINISHED |
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: Heracles | Statement: [Athens (through the story of Theseus), mythicAlliance, Heracles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mythicAlliance Context triple: [Athens (through the story of Theseus), mythicAlliance, Heracles]
-
A.
mythicReputation
Indicates a reputation or renown of legendary, larger-than-life status associated with an entity.
-
B.
mythicInstitution
Indicates a relationship where an institution is characterized as belonging to the realm of myth, legend, or sacred narrative rather than ordinary historical or contemporary reality.
-
C.
mythicAttribute
Indicates that one entity possesses or is characterized by a legendary, mythical, or folklore-based quality, power, or status in relation to another.
-
D.
hasMythicTheme
Indicates that something embodies, references, or is characterized by a mythic or mythological theme.
-
E.
notableMythicKing
Indicates that the subject is recognized as a prominent or distinguished king within myth or legend.
- 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f62e83045c8190a424a2e401a88e9e |
completed | May 2, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62d886828819080ec2f742b9449e3 |
completed | May 2, 2026, 4:59 p.m. |
Created at: April 26, 2026, 7:34 p.m.