Triple
T7466910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gauda Kingdom |
E176393
|
entity |
| Predicate | conflictWith |
P4897
|
FINISHED |
| Object | Harsha |
E448492
|
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: Harsha | Statement: [Gauda Kingdom, conflictWith, Harsha]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Harsha Context triple: [Gauda Kingdom, conflictWith, Harsha]
-
A.
Harsha
chosen
Harsha was a 7th-century Indian emperor who unified much of northern India and became renowned for his patronage of Buddhism, literature, and the arts.
-
B.
Haripal
Haripal is a town in West Bengal, India, known for its railway junction and role as a local commercial and agricultural center within Hooghly district.
-
C.
Harish
Harish is the given name of Harish-Chandra, a prominent Indian-American mathematician and physicist known for his foundational work in representation theory.
-
D.
Akrura
Akrura is a revered figure in Hindu mythology, known as a devout Yadava charioteer and ally of Krishna who played a key role in bringing him to Mathura.
-
E.
Sudarshan
Sudarshan is a common Indian surname found across various regions and communities in India.
- 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_69c69f223fd88190b4c69b95d7cbeeda |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f3f589cc81909f25268838c7c964 |
completed | March 27, 2026, 9:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8346ff7d881909dc2bef5d26d0acf |
completed | March 28, 2026, 8:05 p.m. |
Created at: March 27, 2026, 3:40 p.m.