Triple
T15060535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shahzada |
E379611
|
entity |
| Predicate | transliterationVariant |
P5923
|
FINISHED |
| Object | Shahzade |
E379611
|
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: Shahzade | Statement: [Shahzada, transliterationVariant, Shahzade]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shahzade Context triple: [Shahzada, transliterationVariant, Shahzade]
-
A.
Shahzada
chosen
Shahzada is a royal title used in Persianate and South Asian cultures to denote a prince or son of a monarch.
-
B.
Mirza
Mirza is a historical noble title of Persian and Central Asian origin, commonly borne by princes and high-ranking members of royal and aristocratic families.
-
C.
Shuja
Shuja is a given name most notably associated with Shuja Shah Durrani, a 19th-century ruler of the Durrani Empire in Afghanistan.
-
D.
Sultan
Sultan is a writer known for creating works under the pseudonym "2U."
-
E.
Sultan
Sultan is a surname of Arabic origin historically associated with rulership and authority in various Muslim societies.
- 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dedee6a55c8190b40c4672fb46b79b |
completed | April 15, 2026, 12:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69febfdc8f64819083c7e3510e671b9a |
completed | May 9, 2026, 5:02 a.m. |
Created at: April 10, 2026, 3:01 a.m.