Triple
T9702681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mermerus |
E234815
|
entity |
| Predicate | siblingOf |
P363
|
FINISHED |
| Object | Pheres |
E818580
|
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: Pheres | Statement: [Mermerus, siblingOf, Pheres]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pheres Context triple: [Mermerus, siblingOf, Pheres]
-
A.
Pheres
Pheres is a figure in Greek mythology known as one of the sons of the hero Jason.
-
B.
Pheres
chosen
Pheres is a figure in Greek mythology known as a son of Cretheus and a member of the royal lineage of Thessaly.
-
C.
Theosebia
Theosebia is a relatively obscure early Christian figure known primarily as a member of the family of Basil the Elder, associated with the influential Cappadocian Christian milieu.
-
D.
Phylonoe
Phylonoe is a minor figure in Greek mythology, known primarily through her familial connections within mythic genealogies.
-
E.
Phevos
Phevos is one of the official mascots of the 2004 Athens Olympic Games, inspired by ancient Greek culture and mythology.
- 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_69ca84cc78808190a56f3402b7c139a7 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d7283188190bd50e18f643ad0d3 |
completed | April 1, 2026, 10:34 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1c40329448190bccac60a20dcb9d1 |
completed | April 5, 2026, 2:08 a.m. |
Created at: March 30, 2026, 8:18 p.m.