Triple
T7028510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mohsin |
E163210
|
entity |
| Predicate | transliterationVariant |
P5923
|
FINISHED |
| Object | Mohssen |
E637608
|
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: Mohssen | Statement: [Mohsin, transliterationVariant, Mohssen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mohssen Context triple: [Mohsin, transliterationVariant, Mohssen]
-
A.
Mohsen
chosen
Mohsen is a masculine given name of Persian and Arabic origin, commonly used in Iran and other Muslim-majority countries.
-
B.
Hamed
Hamed is a masculine given name commonly used in Arabic-speaking and Muslim-majority cultures.
-
C.
Mansour
Mansour is an Arabic surname commonly borne by individuals across the Middle East and North Africa, often associated with notable figures in politics, business, and the arts.
-
D.
Mehdi
Mehdi is a common Persian male given name, often associated with Islamic and especially Shia traditions, meaning "the guided one."
-
E.
Malek
Malek is a given name and surname of Arabic origin commonly used across the Middle East and other Muslim-majority regions.
- 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_69c6885d691c81908cf7d31083113886 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e200ecdc819098ca07473dfb272a |
completed | March 27, 2026, 8:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7885d83d4819099cc334dd2841f3b |
completed | March 28, 2026, 7:50 a.m. |
Created at: March 27, 2026, 2:35 p.m.