Triple
T12909001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qasim ibn al-Hassan |
E308801
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Qasim |
E584554
|
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: Qasim | Statement: [Qasim ibn al-Hassan, givenName, Qasim]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Qasim Context triple: [Qasim ibn al-Hassan, givenName, Qasim]
-
A.
Qasim
chosen
Qasim is a central character in Naguib Mahfouz’s novel "Children of Gebelawi," representing a modern, socially conscious figure modeled on the Prophet Muhammad within the book’s allegorical retelling of religious history.
-
B.
Hammad
Hammad is a character in the novel "Falling Man," which explores the aftermath of the September 11 attacks.
-
C.
Ishaq
Ishaq is the Arabic form of the biblical name Isaac, commonly used in Muslim and Arabic-speaking communities.
-
D.
Sa’id
Sa’id is a male given name of Arabic origin, commonly meaning "happy" or "fortunate."
-
E.
Qasim ibn Muhammad
Qasim ibn Muhammad was the eldest son of the Islamic prophet Muhammad, who died in childhood in Mecca.
- 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9719e584c81909be1ac1366effca0 |
completed | April 10, 2026, 9:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6a5680d748190b8453793219bda8f |
completed | May 3, 2026, 1:31 a.m. |
Created at: April 9, 2026, 5:41 p.m.