Triple
T6055151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hermione |
E134890
|
entity |
| Predicate | spouse |
P13
|
FINISHED |
| Object | Neoptolemus |
E457115
|
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: Neoptolemus | Statement: [Hermione, spouse, Neoptolemus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Neoptolemus Context triple: [Hermione, spouse, Neoptolemus]
-
A.
Neoptolemus
chosen
Neoptolemus is a figure in Greek mythology, the son of Achilles who played a crucial role in the fall of Troy and its aftermath.
-
B.
Neoptolemus I of Epirus
Neoptolemus I of Epirus was a 4th-century BC Molossian king of Epirus and an important figure in the dynastic politics of northwestern Greece.
-
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.
Antilochus
Antilochus is a figure in Greek mythology, a son of Nestor renowned for his bravery and close friendship with Achilles during the Trojan War.
- 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_69c00877b6d4819096b0e163728b73a3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0570a863c819090291775245708d6 |
completed | March 22, 2026, 8:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c113b06d188190839cfc48a2461d65 |
completed | March 23, 2026, 10:19 a.m. |
Created at: March 22, 2026, 4:09 p.m.