Triple
T19020385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arisbe |
E465466
|
entity |
| Predicate | sibling |
P363
|
FINISHED |
| Object | Adrastus |
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 | Statement: [Arisbe, sibling, Adrastus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Adrastus Context triple: [Arisbe, sibling, Adrastus]
-
A.
Adrastus
chosen
Adrastus is a legendary king of Argos in Greek mythology, best known as the leader of the Seven Against Thebes.
-
B.
Deiphontes
Deiphontes is a figure in Greek mythology known as a Heraclid prince and son-in-law of Temenus, associated with the royal lineage of Argos.
-
C.
Dagisthaeus
Dagisthaeus was a 6th-century Byzantine general known for leading imperial forces during the Lazic War against the Sasanian Empire.
-
D.
Heleus
Heleus is a figure in Greek mythology known as a son of Perseus and Andromeda.
-
E.
Tithraustes
Tithraustes was a Persian military commander who led Achaemenid forces against the Greeks during the early 5th century BCE.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6de93408190a98dea2319f1af62 |
completed | April 20, 2026, 7:33 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a05c543208481908bd663c7bdd9c059 |
completed | May 14, 2026, 12:51 p.m. |
Created at: April 10, 2026, 12:02 p.m.