Triple
T18417275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basile |
E441925
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | Basileios |
—
|
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: Basileios | Statement: [Basile, relatedTo, Basileios]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Basileios Context triple: [Basile, relatedTo, Basileios]
-
A.
Dorotheos
Dorotheos is a Greek given name of religious origin, meaning "gift of God."
-
B.
Basileus Demetrios
Basileus Demetrios is the royal title used by Demetrius I of Bactria, a Hellenistic king known for expanding Greek rule into parts of India in the 2nd century BCE.
-
C.
Basile
Basile is a given name and surname, commonly used in French and Italian contexts, derived from the name Basil.
-
D.
Basilios
chosen
Basilios is a Greek male given name, often used in Orthodox Christian cultures and derived from the word for "king" or "royal."
-
E.
Basileus Antialkidas
Basileus Antialkidas was an Indo-Greek king known from his coinage, which reflects a blend of Hellenistic and Indian cultural and religious influences.
- 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_69d8b9eb8a508190a942fd75ebd8b1dc |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e51a291f148190b289b5b617077797 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 10:47 a.m.