Triple
T14051391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tulsidas |
E338098
|
entity |
| Predicate | wrote |
P2831
|
FINISHED |
| Object | Dohavali |
E1076765
|
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: Dohavali | Statement: [Tulsidas, wrote, Dohavali]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dohavali Context triple: [Tulsidas, wrote, Dohavali]
-
A.
Dohavali
chosen
Dohavali is a poetic work in Hindi by the saint-poet Tulsidas, composed in rhyming couplets that convey devotional and moral teachings.
-
B.
Dhuleti
Dhuleti is the vibrant second day of the Hindu festival of Holi, celebrated with the playful throwing of colored powders and water.
-
C.
Ranavav
Ranavav is a small town in the Indian state of Gujarat, known for its proximity to Porbandar and local industries such as cement manufacturing.
-
D.
Dhundhari
Dhundhari is an Indo-Aryan language spoken primarily in and around Jaipur and adjoining regions of Rajasthan, India.
-
E.
Pipavav
Pipavav is a coastal town in Gujarat, India, known primarily for hosting one of the country’s major private ports and associated shipbuilding and maritime industries.
- 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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de3c8a518081908ad030ba48b7b946 |
completed | April 14, 2026, 1:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcd099b7788190a7c309dba450e58f |
completed | May 7, 2026, 5:49 p.m. |
Created at: April 9, 2026, 10:20 p.m.