Triple
T156640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zeus |
E3194
|
entity |
| Predicate | child |
P120
|
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: [Zeus, child, Heracles]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heracles Context triple: [Zeus, child, 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.
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.
-
C.
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.
-
D.
Ares
Ares is the Greek god of war, embodying the brutal and chaotic aspects of battle in ancient Greek mythology.
-
E.
Sterope
Sterope is a figure from Greek mythology, traditionally considered one of the Pleiades and a daughter of the Titan Atlas.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a25830136881909f5ecb2cb22097b2 |
completed | Feb. 28, 2026, 2:51 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a2fd02709c819096db4f4c242d463f |
completed | Feb. 28, 2026, 2:34 p.m. |
Created at: Feb. 28, 2026, 2:31 a.m.