Triple
T4757506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nestor |
E105623
|
entity |
| Predicate | sibling |
P363
|
FINISHED |
| Object | Periclymenus |
E454471
|
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: Periclymenus | Statement: [Nestor, sibling, Periclymenus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Periclymenus Context triple: [Nestor, sibling, Periclymenus]
-
A.
Periclymenus
chosen
Periclymenus is a figure in Greek mythology, famed as one of the sons of Neleus and Poseidon who was granted the power of shape-shifting in battle.
-
B.
Steropes
Steropes is a one-eyed giant from Greek mythology, one of the Cyclopes known for forging Zeus’s thunderbolts.
-
C.
Pholus
Pholus is a wise centaur from Greek mythology, best known for his role in the stories surrounding Heracles and the fateful encounter with the poisoned arrows of the Hydra.
-
D.
Demophon
Demophon is a figure in Greek mythology, traditionally known as one of the sons of the Athenian hero Theseus and later a king of Athens.
-
E.
Enipeus
Enipeus is a river god in Greek mythology, personifying a famous river of Thessaly and known for being the object of Tyro’s love.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64ec16a0819089836e4388b555f6 |
completed | March 20, 2026, 3:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be3a72ba908190ad9b423aea2a22b8 |
completed | March 21, 2026, 6:28 a.m. |
Created at: March 20, 2026, 1:20 p.m.