Triple
T18695897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Λαέρτης |
E457113
|
entity |
| Predicate | father |
P120
|
FINISHED |
| Object | Arcesius |
—
|
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: Arcesius | Statement: [Λαέρτης, father, Arcesius]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Arcesius Context triple: [Λαέρτης, father, Arcesius]
-
A.
Arcesius
chosen
Arcesius is a figure in Greek mythology, known as the son of Zeus and the father of Laertes, making him the grandfather of Odysseus.
-
B.
Callinicus
Callinicus is the honorific epithet meaning “gloriously victorious” borne by the Hellenistic ruler Seleucus II.
-
C.
Didius
Didius was the family name of the Roman emperor Didius Julianus, associated with a senatorial lineage in ancient Rome.
-
D.
Aelius
Aelius is an ancient Roman family name (nomen) associated with several notable figures of the Roman Empire, including emperors and high-ranking officials.
-
E.
Arses
Arses, better known by his regnal name Artaxerxes II, was a king of the Achaemenid Persian Empire who ruled in the 4th century BCE.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e562e775408190996b4c613b83f185 |
completed | April 19, 2026, 11:19 p.m. |
Created at: April 10, 2026, 11:49 a.m.