Triple
T13168703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chand dynasty |
E312918
|
entity |
| Predicate | foundedBy |
P104
|
FINISHED |
| Object | Som Chand |
E1025459
|
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: Som Chand | Statement: [Chand dynasty, foundedBy, Som Chand]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Som Chand Context triple: [Chand dynasty, foundedBy, Som Chand]
-
A.
Som Chand
chosen
Som Chand was a prominent ruler of the Chand dynasty, known for establishing and consolidating its power in the Kumaon region of present-day Uttarakhand, India.
-
B.
Chanda
Chanda was a historical kingdom associated with the Gond people, an indigenous community of central India.
-
C.
Chandri
Chandri is a pivotal female character in the Indian novel "Samskara," known for challenging social and religious norms within a conservative Brahmin community.
-
D.
Sahodhari
Sahodhari is an Indian Tamil-language film produced by the prominent Chennai-based studio AVM Productions.
-
E.
Sohi
Sohi is a Punjabi-origin surname commonly found among people from the Indian subcontinent and their diaspora.
- 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_69d806ac3ee081909b2fd27d060aa974 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98c2e03c481909909b8f10c7e8ffc |
completed | April 10, 2026, 11:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6f5e22458819097dc8d6708df5284 |
completed | May 3, 2026, 7:14 a.m. |
Created at: April 9, 2026, 9:13 p.m.