Triple
T4956397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polynices |
E111290
|
entity |
| Predicate | allies |
P2865
|
FINISHED |
| Object | Adrastus of Argos |
E174450
|
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: Adrastus of Argos | Statement: [Polynices, allies, Adrastus of Argos]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Adrastus of Argos Context triple: [Polynices, allies, Adrastus of Argos]
-
A.
Adrastus
chosen
Adrastus is a legendary king of Argos in Greek mythology, best known as the leader of the Seven Against Thebes.
-
B.
Temenus of Argos
Temenus of Argos is a legendary Heraclid king of Argos in Greek mythology, regarded as an ancestor of the Argead dynasty of Macedon.
-
C.
Sthenelus of Mycenae
Sthenelus of Mycenae is a figure in Greek mythology, a Mycenaean prince known primarily as the son of King Eurystheus.
-
D.
Aristodemus
Aristodemus is a minor figure in ancient Greek philosophy, known primarily as a participant and narrator in Plato’s dialogue Symposium.
-
E.
Heleus
Heleus is a figure in Greek mythology known as a son of Perseus and Andromeda.
- 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd71d6ba9c8190932f8d81240c3f56 |
completed | March 20, 2026, 4:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be9244fb008190baee4ade5b00691f |
completed | March 21, 2026, 12:42 p.m. |
Created at: March 20, 2026, 1:32 p.m.