Triple
T11756233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Takmak Tok |
E279531
|
entity |
| Predicate | nearbyCity |
P350
|
FINISHED |
| Object | Mangaon |
E919078
|
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: Mangaon | Statement: [Takmak Tok, nearbyCity, Mangaon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mangaon Context triple: [Takmak Tok, nearbyCity, Mangaon]
-
A.
Mangaon
chosen
Mangaon is a town in the Raigad district of Maharashtra, India, known as a local commercial and transport hub in the Konkan region.
-
B.
Malkapur
Malkapur is a town and municipal council in Maharashtra, India, known as a commercial and transport hub within Buldhana district.
-
C.
Manikonda
Manikonda is a rapidly developing residential and IT suburb in the western part of Hyderabad, known for its proximity to major technology hubs and corporate campuses.
-
D.
Kotagiri
Kotagiri is a hill station town in the Nilgiri district of Tamil Nadu, India, known for its cool climate, tea plantations, and scenic mountain landscapes.
-
E.
Manpada
Manpada is a residential suburb located in the city of Thane in the Mumbai Metropolitan Region of Maharashtra, 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a50c8d708190ad79ecb57b715d04 |
completed | April 10, 2026, 7:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f01a2f0a848190944ba2688c6d7ad2 |
completed | April 28, 2026, 2:23 a.m. |
Created at: April 8, 2026, 9:41 p.m.