Triple
T23240132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matsya |
E581416
|
entity |
| Predicate | neighboringEntity |
P350
|
FINISHED |
| Object | Surasena |
—
|
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: Surasena | Statement: [Matsya, neighboringEntity, Surasena]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Surasena Context triple: [Matsya, neighboringEntity, Surasena]
-
A.
Surasena
chosen
Surasena was an ancient Indian kingdom and one of the sixteen Mahajanapadas, centered around its capital Mathura in the northern Indian subcontinent.
-
B.
Ugrasena
Ugrasena is a legendary king in Hindu mythology, known as a ruler of the Yadava clan and the grandfather of Krishna.
-
C.
Ashvasena
Ashvasena is known in Jain tradition as the father of Parshvanatha, the 23rd Tirthankara.
-
D.
Shurasena
Shurasena was an ancient Yadava king of the Vrishni clan, known in Hindu tradition as the grandfather of Krishna and a prominent ruler in the Mahabharata era.
-
E.
Santivarma
Santivarma was a ruler of the ancient Kadamba dynasty, an early Kannada-speaking royal house that governed parts of present-day Karnataka in southern India.
- 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_69e2460556f88190be1744a84a84173f |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f192ecc7e481908cac59df5c0deea1 |
completed | April 29, 2026, 5:11 a.m. |
Created at: April 17, 2026, 4:10 p.m.