Triple
T19290113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barara tehsil |
E482417
|
entity |
| Predicate | hasAdministrativeCentre |
P1474
|
FINISHED |
| Object | Barara |
—
|
NE NERFINISHED |
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: Barara | Statement: [Barara tehsil, hasAdministrativeCentre, Barara]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Barara Context triple: [Barara tehsil, hasAdministrativeCentre, Barara]
-
A.
Barara
chosen
Barara is a town in the Ambala district of the northern Indian state of Haryana, known primarily as a local administrative and market center for surrounding rural areas.
-
B.
Balara
Balara is a municipality-level city in southeastern Nepal’s Madhesh Province, known for its agrarian economy and proximity to the Indian border.
-
C.
Bara
Bara is a town in central Sudan known as an agricultural and trading center in North Kordofan State.
-
D.
Bara
Bara is a town in Pakistan’s Khyber District, known as a key settlement in the Khyber Pass region with strategic and commercial significance.
-
E.
Bariadi
Bariadi is a town in northern Tanzania that serves as an important local administrative and commercial center.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc050a888190ac204d1e736200c5 |
completed | April 20, 2026, 10:12 a.m. |
Created at: April 10, 2026, 1:30 p.m.