Triple
T14590174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sadaat-e-Zaidpur |
E342422
|
entity |
| Predicate | culturalIdentity |
P958
|
FINISHED |
| Object | Ashraf |
E181202
|
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: Ashraf | Statement: [Sadaat-e-Zaidpur, culturalIdentity, Ashraf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ashraf Context triple: [Sadaat-e-Zaidpur, culturalIdentity, Ashraf]
-
A.
Ashraf
chosen
Ashraf is a masculine given name of Arabic origin commonly used in various Muslim-majority countries.
-
B.
Nabil
Nabil is a common Arabic given name meaning "noble" or "honorable," used across many Arabic-speaking and Muslim-majority cultures.
-
C.
Sharif
Sharif is an honorific title in the Islamic world traditionally denoting a noble person descended from the Prophet Muhammad, particularly through the lineage of the Sayyids.
-
D.
Fathi
Fathi is an Arabic masculine given name commonly used in the Middle East and North Africa.
-
E.
Taher
Taher is a town and commune in northeastern Algeria, serving as an important local center within Jijel Province.
- 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_69d822ddc0f081909cd8163c7de298cd |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4249af08190962009741d1f7d41 |
completed | April 14, 2026, 9:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdd5c79c488190a134d2b0435e899e |
completed | May 8, 2026, 12:23 p.m. |
Created at: April 10, 2026, 1:24 a.m.