Triple
T14251104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nawabshah District |
E353263
|
entity |
| Predicate | hasTown |
P847
|
FINISHED |
| Object | Sakrand |
E1038114
|
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: Sakrand | Statement: [Nawabshah District, hasTown, Sakrand]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sakrand Context triple: [Nawabshah District, hasTown, Sakrand]
-
A.
Sakrand
chosen
Sakrand is a town in Pakistan’s Sindh province that serves as a local commercial and agricultural center within the Shaheed Benazirabad District.
-
B.
Saratak
Saratak is a rural village located in Armenia's Shirak Province.
-
C.
Sakia
Sakia is a prominent cultural center and arts venue in Cairo, Egypt, known for hosting concerts, exhibitions, and a wide range of cultural events.
-
D.
Saklan
Saklan is a Native American group historically associated with the Bay Miwok peoples of the San Francisco Bay Area in California.
-
E.
Sancar
Sancar is the surname of Aziz Sancar, a Turkish-American biochemist and molecular biologist renowned for his Nobel Prize–winning work on DNA repair.
- 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6296f9d0819086f62f525d07eb12 |
completed | April 14, 2026, 3:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd325815d48190b070866f41986847 |
completed | May 8, 2026, 12:46 a.m. |
Created at: April 10, 2026, 1:08 a.m.