Triple
T5505480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bindusara |
E144428
|
entity |
| Predicate | child |
P120
|
FINISHED |
| Object |
Susima
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.
|
E533486
|
NE FINISHED |
How this triple was built (4 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.
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.
-
B.
Susuman
Susuman is a small mining town in Russia's Magadan Oblast, located in the remote Russian Far East.
-
C.
Dasuya
Dasuya is a town and municipal council in the Hoshiarpur district of Punjab, India, known historically as a significant settlement in the region.
-
D.
Sonamura
Sonamura is a town in the Indian state of Tripura, known as an administrative and commercial center near the India–Bangladesh border.
-
E.
Shamiya
Shamiya is a residential district in Kuwait City known for its planned layout, community facilities, and central location within the capital.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Susima Triple: [Bindusara, child, Susima]
Generated description
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.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Susima Target entity description: 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.
-
A.
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.
-
B.
Susuman
Susuman is a small mining town in Russia's Magadan Oblast, located in the remote Russian Far East.
-
C.
Dasuya
Dasuya is a town and municipal council in the Hoshiarpur district of Punjab, India, known historically as a significant settlement in the region.
-
D.
Sonamura
Sonamura is a town in the Indian state of Tripura, known as an administrative and commercial center near the India–Bangladesh border.
-
E.
Shamiya
Shamiya is a residential district in Kuwait City known for its planned layout, community facilities, and central location within the capital.
- F. None of above. chosen
Provenance (5 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_69c008f6b5048190a09064116062cf69 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f0e91d08190a4db907030955bb3 |
completed | March 22, 2026, 4:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c027b3ab408190ab1e68dfbcf7eec6 |
completed | March 22, 2026, 5:32 p.m. |
| NEDg | Description generation | batch_69c0430e51fc819084706f52a815350a |
completed | March 22, 2026, 7:29 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69c046e54a20819080eef5179f206314 |
completed | March 22, 2026, 7:45 p.m. |
Created at: March 22, 2026, 3:32 p.m.