Triple
T5551250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eris |
E145529
|
entity |
| Predicate | sibling |
P363
|
FINISHED |
| Object | Momus |
E249774
|
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: Momus | Statement: [Eris, sibling, Momus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Momus Context triple: [Eris, sibling, Momus]
-
A.
Momus
chosen
Momus is the Greek god of satire, mockery, and blame, known for criticizing both gods and mortals.
-
B.
Silenus
Silenus is a figure from Greek mythology, often depicted as an older, drunken companion and tutor of the god Dionysus and associated with wisdom and rustic revelry.
-
C.
Philomelus
Philomelus was a Phocian military leader who initiated and led the early phases of the Third Sacred War in ancient Greece.
-
D.
Philomelus
Philomelus is a minor figure in Greek mythology known primarily as a son of the goddess Demeter.
-
E.
Sophillus
Sophillus was the father of the ancient Greek tragedian Sophocles, about whom little is known beyond his paternal connection to the playwright.
- 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_69c008fb879c81909f5bfa56fadc1d46 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01fe3e7788190aa5361b083197c17 |
completed | March 22, 2026, 4:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c028350bc08190a8b48893157b86a1 |
completed | March 22, 2026, 5:34 p.m. |
Created at: March 22, 2026, 3:35 p.m.