Triple
T19601022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elymian |
E470475
|
entity |
| Predicate | hasMajorSettlement |
P316
|
FINISHED |
| Object | Eryx |
—
|
NE NERFINISHED |
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: Eryx | Statement: [Elymian, hasMajorSettlement, Eryx]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eryx Context triple: [Elymian, hasMajorSettlement, Eryx]
-
A.
Eryx
chosen
Eryx is a figure in Greek mythology, a son of Aphrodite known as a powerful king and boxer associated with the city and region of Eryx in Sicily.
-
B.
Lophodolos
Lophodolos is a genus of deep-sea anglerfish in the family Oneirodidae, known for their bioluminescent lures used to attract prey in the dark ocean depths.
-
C.
Hyillus
Hyillus is a figure from Greek mythology, known as a descendant of the royal line of Argos.
-
D.
Ochimus
Ochimus is a figure in Greek mythology, known as a son of the sea nymph Rhode and associated with the early rulers of the island of Rhodes.
-
E.
Iberus
Iberus is the ancient Latin name for the Ebro River, one of the major rivers of the Iberian Peninsula in present-day Spain.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6407f1fd88190aa82c4c96f755584 |
completed | April 20, 2026, 3:04 p.m. |
Created at: April 10, 2026, 1:43 p.m.