Triple
T12744611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isidore |
E304573
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Isidoros |
E306162
|
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: Isidoros | Statement: [Isidore, hasVariant, Isidoros]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Isidoros Context triple: [Isidore, hasVariant, Isidoros]
-
A.
Isidoros
chosen
Isidoros is a masculine given name of Greek origin, commonly considered a variant of Isidore and meaning "gift of Isis."
-
B.
Erasinos
Erasinos is an ancient river in the region of Attica, Greece, historically associated with the sanctuary and coastal area of Brauron.
-
C.
Neos Panteleimonas
Neos Panteleimonas is a coastal village in the Pieria regional unit of Greece, known for its beaches and views of Mount Olympus.
-
D.
Eugenios
Eugenios is a variant form of the given name Eugenio, commonly used in Greek and related linguistic traditions.
-
E.
Damaskinos
Damaskinos is a Greek-origin surname historically associated with notable religious and cultural figures.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96bd42fe08190a85467b1a998d2af |
completed | April 10, 2026, 9:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f684ee2ab4819099194d115d2e5a15 |
completed | May 2, 2026, 11:12 p.m. |
Created at: April 9, 2026, 5:26 p.m.