Triple
T10171361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prasun people |
E235336
|
entity |
| Predicate | hasAutonym |
P1435
|
FINISHED |
| Object | Prasun |
E228812
|
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: Prasun | Statement: [Prasun people, hasAutonym, Prasun]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Prasun Context triple: [Prasun people, hasAutonym, Prasun]
-
A.
Prasun
Prasun is a given name used in South Asian contexts, often associated with Indian or Nepali origins.
-
B.
Prasun
chosen
Prasun is an indigenous ethnic group from the Nuristan region of Afghanistan, known for its distinct culture and language within the Indo-Iranian family.
-
C.
Prasouda
Prasouda is a small Greek island located in the Pagasetic Gulf, known for its tranquil natural setting and proximity to the coast of Thessaly.
-
D.
Parthibo
Parthibo is a Bengali literary work by acclaimed author Shirshendu Mukhopadhyay, known for its distinctive storytelling and exploration of human relationships.
-
E.
Basu
Basu is an Indian surname, particularly common among Bengali communities, that is closely related to and sometimes used as a variant of the surname Bose.
- 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdec9e4e0c819097dceb7bf7757948 |
completed | April 2, 2026, 4:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d30101e3ec819095a587c0dae55f71 |
completed | April 6, 2026, 12:40 a.m. |
Created at: March 30, 2026, 9:10 p.m.