Triple
T15949942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Van Helsing (TV series) |
E386787
|
entity |
| Predicate | hasCharacter |
P2308
|
FINISHED |
| Object | Mohamad |
E638039
|
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: Mohamad | Statement: [Van Helsing (TV series), hasCharacter, Mohamad]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mohamad Context triple: [Van Helsing (TV series), hasCharacter, Mohamad]
-
A.
Mohamad
chosen
Mohamad is a masculine given name of Arabic origin, commonly used as a variant spelling of Muhammad.
-
B.
Ahmad
Ahmad is the narrator of the film "Soul Food," providing the story’s perspective and emotional throughline.
-
C.
Ahmad
Ahmad is a common Arabic male given name meaning "most commendable" or "most praiseworthy," widely used across the Muslim world.
-
D.
Ahmad
Ahmad is the central protagonist of the story "Man Push Cart," a former Pakistani rock star struggling to make a living as a street vendor in New York City.
-
E.
Ahmad
Ahmad is the deposed king and heroic protagonist in the 1940 fantasy film "The Thief of Bagdad."
- 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_69d86da882448190a82ea962fe343b79 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e156d4c5008190a56ebf8c28f712dc |
completed | April 16, 2026, 9:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffc3c1b49c819087e5a088d41963ec |
completed | May 9, 2026, 11:31 p.m. |
Created at: April 10, 2026, 4:53 a.m.