Triple
T10689377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ardabil Province |
E251967
|
entity |
| Predicate | hasCity |
P316
|
FINISHED |
| Object | Parsabad |
E783570
|
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: Parsabad | Statement: [Ardabil Province, hasCity, Parsabad]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Parsabad Context triple: [Ardabil Province, hasCity, Parsabad]
-
A.
Parsabad
chosen
Parsabad is a significant urban and agricultural center in Iran’s Ardabil Province, near the border with Azerbaijan.
-
B.
Brahmapuri
Brahmapuri is a town in Maharashtra, India, known as one of the important urban centers within Chandrapur district.
-
C.
Pavapuri
Pavapuri is a revered Jain pilgrimage site in Bihar, India, best known as the place where Mahavira, the 24th Tirthankara, attained nirvana.
-
D.
Jwalapur
Jwalapur is a prominent suburban town and commercial hub near Haridwar in the Indian state of Uttarakhand.
-
E.
Kawardha
Kawardha is a regional dialect of the Chhattisgarhi language spoken in parts of the Indian state of Chhattisgarh.
- 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fd1aef888190ba92474af3a49e36 |
completed | April 9, 2026, 1:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d988a59d6c8190a0e170acfb3af6da |
completed | April 10, 2026, 11:32 p.m. |
Created at: April 8, 2026, 9:11 p.m.