Triple
T18389270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shabana Rehman |
E449677
|
entity |
| Predicate | hasSurname |
P18
|
FINISHED |
| Object | Rehman |
—
|
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: Rehman | Statement: [Shabana Rehman, hasSurname, Rehman]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rehman Context triple: [Shabana Rehman, hasSurname, Rehman]
-
A.
Rehman
chosen
Rehman is a surname shared by various individuals, including the late Norwegian-Pakistani comedian and writer Shabana Rehman.
-
B.
Nasir Jung
Nasir Jung was an 18th-century Nizam of Hyderabad in the Deccan, known for his role in the Carnatic Wars and complex alliances with European colonial powers.
-
C.
Alim Khan
Alim Khan was a prominent early 19th-century khan of the Kokand Khanate in Central Asia, known for expanding its territory and consolidating its political power.
-
D.
Naushad
Naushad was a legendary Indian film music director and composer renowned for his classical-based scores in Hindi cinema’s golden era.
-
E.
Ali Murad
Ali Murad is a historical figure associated with the Talpur dynasty, known primarily as Mir Ali Murad Khan Talpur, a ruler in 19th-century Sindh.
- 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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e51840884c81908e84e9206b4739ee |
completed | April 19, 2026, 6 p.m. |
Created at: April 10, 2026, 10:46 a.m.