Triple
T11905128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Gujarat |
E283253
|
entity |
| Predicate | includesCity |
P3207
|
FINISHED |
| Object | Modasa |
E639757
|
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: Modasa | Statement: [North Gujarat, includesCity, Modasa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Modasa Context triple: [North Gujarat, includesCity, Modasa]
-
A.
Modasa
chosen
Modasa is a town in the Indian state of Gujarat that serves as the administrative headquarters of Aravalli district.
-
B.
Kawardha
Kawardha is a regional dialect of the Chhattisgarhi language spoken in parts of the Indian state of Chhattisgarh.
-
C.
Marw
Marw (Merv) was an important ancient city in Khorasan, serving as a major political, military, and cultural center in early Islamic and pre-Islamic Central Asia.
-
D.
Murud
Murud refers to an indigenous ethnic subgroup closely related to the Lun Bawang people of Borneo, sharing similar cultural and linguistic heritage.
-
E.
Murud
Murud is a coastal town in Maharashtra, India, known for its scenic beaches and the historic Murud-Janjira sea fort.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e525460c81909d855048d9c799bf |
completed | April 10, 2026, 11:55 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f418487f448190b6e24fb2c0409e3f |
completed | May 1, 2026, 3:04 a.m. |
Created at: April 8, 2026, 9:44 p.m.