Triple
T4879151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Menelaus |
E109281
|
entity |
| Predicate | ally |
P4662
|
FINISHED |
| Object | Diomedes |
E409398
|
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: Diomedes | Statement: [Menelaus, ally, Diomedes]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Diomedes Context triple: [Menelaus, ally, Diomedes]
-
A.
Diomedes
chosen
Diomedes is a hero from Greek mythology, famed for his role in the Trojan War as one of the Achaeans’ greatest warriors and a favored ally of the goddess Athena.
-
B.
Diomedon
Diomedon was an Athenian naval commander during the Peloponnesian War, noted for his role in major late-war battles against Sparta.
-
C.
Diomed
Diomed was an 18th-century British Thoroughbred racehorse best known for winning the inaugural Epsom Derby and later becoming an influential sire in American bloodlines.
-
D.
Palamedes
Palamedes is a 1625 Dutch tragedy by Joost van den Vondel that allegorically critiques political and religious injustice in the Dutch Republic.
-
E.
Sarpedon
Sarpedon is a figure in Greek mythology, often known as a son of Zeus and a prominent warrior in 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_69bd440e9d64819083e82cf33b4d9570 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6dbf37ac819085bb758bc6406271 |
completed | March 20, 2026, 3:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be6fb8e8f081908cee75f80494dd7d |
completed | March 21, 2026, 10:15 a.m. |
Created at: March 20, 2026, 1:27 p.m.