Triple
T21058697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perseid dynasty |
E518793
|
entity |
| Predicate | hasMember |
P10
|
FINISHED |
| Object | Telephus |
—
|
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: Telephus | Statement: [Perseid dynasty, hasMember, Telephus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Telephus Context triple: [Perseid dynasty, hasMember, Telephus]
-
A.
Telephus
chosen
Telephus is a hero in Greek mythology, a son of Heracles who became king of Mysia and played a crucial role in the events leading up to the Trojan War.
-
B.
Inachus
Inachus is a river god in Greek mythology, regarded as the first king of Argos and the progenitor of several important mythological figures.
-
C.
Tlepolemus
Tlepolemus is a figure in Greek mythology, known as a son of Heracles who became a leader of Rhodian forces in the Trojan War.
-
D.
Neocles
Neocles was an Athenian of the late 6th century BC, best known as the father of the prominent statesman and general Themistocles.
-
E.
Thrasymedes
Thrasymedes is a figure in Greek mythology, a son of Nestor who fought as a warrior in the Trojan War.
- 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_69e0b5053ac48190921529544959e906 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fd8236b481908eebfaeeb2aa63e6 |
completed | April 21, 2026, 4:30 a.m. |
Created at: April 16, 2026, 2:37 p.m.