Triple
T15144799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of 1799 |
E361778
|
entity |
| Predicate | hasLocation |
P40
|
FINISHED |
| Object | Mysore |
E80753
|
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: Mysore | Statement: [Treaty of 1799, hasLocation, Mysore]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mysore Context triple: [Treaty of 1799, hasLocation, Mysore]
-
A.
Mysuru
chosen
Mysuru is a historic city in the southern Indian state of Karnataka, renowned for its royal heritage, palaces, and cultural festivals such as Dasara.
-
B.
Belgaum
Belgaum is a major city in the Indian state of Karnataka, known as an important commercial, industrial, and military hub near the Maharashtra–Goa border.
-
C.
Mangalore
Mangalore is a major port city on the southwestern coast of India, known for its maritime trade, diverse culture, and role as a commercial hub of Karnataka.
-
D.
Madikeri
Madikeri is a scenic hill town in Karnataka’s Coorg region, known for its cool climate, coffee plantations, and lush Western Ghats landscapes.
-
E.
Bidar
Bidar is a historic city in the Indian state of Karnataka, renowned for its medieval fort, rich Deccan Sultanate heritage, and distinctive Bidri metalwork.
- 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_69d85a0759908190b8a051d2e2a1cbe6 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005c71b688190b2e8ccfdf4db9037 |
completed | April 15, 2026, 9:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0007757ed48190813f6ab839240a15 |
completed | May 10, 2026, 4:20 a.m. |
Created at: April 10, 2026, 3:07 a.m.