Triple
T22291407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Djavidan Hanem |
E551004
|
entity |
| Predicate | title |
P38
|
FINISHED |
| Object | Hanem |
—
|
NE NERFINISHED |
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: Hanem | Statement: [Djavidan Hanem, title, Hanem]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hanem Context triple: [Djavidan Hanem, title, Hanem]
-
A.
Hanem
chosen
Hanem is an Ottoman-era honorific title used for women of high social standing, similar to "lady" or "madam."
-
B.
Hamey
Hamey is a diminutive or affectionate nickname derived from the given name Hamish.
-
C.
Hennenman
Hennenman is a small town in South Africa’s Free State province, situated within the Lejweleputswa District and known historically for its links to the regional mining and agricultural economy.
-
D.
Hannen
Hannen is an English surname associated with several notable figures, including actors and judges, in British history.
-
E.
Hannum
Hannum is a surname most notably associated with Alex Hannum, a Hall of Fame American basketball coach and former player.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e45fb848190a1b2ae21296e3a5f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1560c47e481908b33de63a11e25de |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 16, 2026, 8:41 p.m.