Triple
T21617593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bindusara |
E533484
|
entity |
| Predicate | child |
P120
|
FINISHED |
| Object | Susima |
—
|
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: Susima | Statement: [Bindusara, child, Susima]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Susima Context triple: [Bindusara, child, Susima]
-
A.
Susima
chosen
Susima was an ancient Indian prince of the Maurya dynasty, known primarily as the elder son of Emperor Bindusara and rival claimant to the throne against his brother Ashoka.
-
B.
Syoma
Syoma is a Russian diminutive form of the male given name Semyon, commonly used as an affectionate nickname.
-
C.
Sumirago
Sumirago is a small town in the Lombardy region of northern Italy, known in fashion circles as the longtime base of the Missoni design house.
-
D.
Sasima
Sasima was an obscure town in ancient Cappadocia, best known as the short-lived and reluctant episcopal see of Gregory of Nazianzus in the 4th century.
-
E.
Sumbe
Sumbe is a coastal city in western Angola that serves as an important administrative and economic center in the Cuanza Sul region.
- 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_69e0c46411108190bba0d4176dffc9f3 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef3bac4a5c8190919c625c14a54c16 |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 16, 2026, 6:34 p.m.