Triple
T21071428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ἁρμονία |
E519115
|
entity |
| Predicate | child |
P120
|
FINISHED |
| Object | Illyrius |
—
|
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: Illyrius | Statement: [Ἁρμονία, child, Illyrius]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Illyrius Context triple: [Ἁρμονία, child, Illyrius]
-
A.
Illyrius
chosen
Illyrius is a figure in Greek mythology regarded as the eponymous ancestor of the Illyrian peoples.
-
B.
Dulo
Dulo was the early medieval ruling dynasty of the Bulgars, traditionally associated with Khan Asparuh and the founding of the First Bulgarian Empire.
-
C.
Gundisalvus
Gundisalvus is a medieval Latin given name of Visigothic origin that later evolved into the Spanish name Gonzalo.
-
D.
Lokris
Lokris was an ancient Greek region in central Greece, traditionally inhabited by the Locrians and divided into the subregions of Opuntian and Ozolian Lokris.
-
E.
Prilidian
Prilidian was an early Christian disciple associated with Babylas of Antioch, remembered within the tradition of the Antiochene church.
- 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_69e0b505ef108190b25dd4033e2ff7eb |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6feb8ed4481909c9f804ccd8da3e2 |
completed | April 21, 2026, 4:36 a.m. |
Created at: April 16, 2026, 2:46 p.m.