Triple
T282187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mycenae and Tiryns |
E5375
|
entity |
| Predicate | linkedToMythology |
P9595
|
FINISHED |
| Object | Heracles |
E20157
|
NE 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: Heracles | Statement: [Mycenae and Tiryns, linkedToMythology, Heracles]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heracles Context triple: [Mycenae and Tiryns, linkedToMythology, Heracles]
-
A.
Heracles
chosen
Heracles is a legendary hero of Greek mythology renowned for his superhuman strength and his completion of the Twelve Labors.
-
B.
Perseus
Perseus is a legendary Greek hero famed for slaying the Gorgon Medusa and rescuing Andromeda.
-
C.
Achilles
Achilles is a legendary Greek hero of the Trojan War, famed for his near invincibility, martial prowess, and central role in Homer's Iliad.
-
D.
Zeus
Zeus is the king of the Olympian gods in Greek mythology, ruling over the sky and thunder and presiding as the chief deity of the pantheon.
-
E.
Odysseus
Odysseus is the cunning Greek hero and king of Ithaca renowned for his long, perilous journey home after the Trojan War as depicted in ancient epic poetry.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a257e6c8788190987dfe705ca2912a |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a260d0dae48190a2ec98d0186fd792 |
completed | Feb. 28, 2026, 3:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a399a74d448190a4857ce008e64e7e |
completed | March 1, 2026, 1:43 a.m. |
Created at: Feb. 28, 2026, 2:59 a.m.