Triple
T6944037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enarete |
E160749
|
entity |
| Predicate | child |
P120
|
FINISHED |
| Object | Perieres |
E520272
|
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: Perieres | Statement: [Enarete, child, Perieres]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Perieres Context triple: [Enarete, child, Perieres]
-
A.
Pleistarchus
Pleistarchus was a 5th-century BC Eurypontid king of Sparta and son of the famous Spartan leader Pausanias.
-
B.
Leonnatus
Leonnatus was a Macedonian nobleman and general who served under Alexander the Great and later emerged as one of the Diadochi, the rival successors who contested control of Alexander’s empire.
-
C.
Apheidas
Apheidas is a minor figure in Greek mythology known primarily as a child of the Muse Erato.
-
D.
Polyperchon
Polyperchon was a Macedonian general and one of Alexander the Great’s successors who briefly served as regent of the empire during the early Wars of the Diadochi.
-
E.
Perieres of Messenia
chosen
Perieres of Messenia is a figure in Greek mythology, a Messenian king associated with the royal line of Perseus through his marriage to Gorgophone.
- 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_69c6884f3db4819080ad65da69386206 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6da88b79c8190a8f297dfc4972979 |
completed | March 27, 2026, 7:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c75866a2408190b472fdad73a8799b |
completed | March 28, 2026, 4:26 a.m. |
Created at: March 27, 2026, 2:28 p.m.