Triple
T21012978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huram |
E517597
|
entity |
| Predicate | hasVariantSpelling |
P457
|
FINISHED |
| Object | Hirom |
—
|
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: Hirom | Statement: [Huram, hasVariantSpelling, Hirom]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hirom Context triple: [Huram, hasVariantSpelling, Hirom]
-
A.
Hirom
chosen
Hirom is a variant form of the name Hiram, which is of Hebrew origin and historically associated with biblical and ancient Near Eastern figures.
-
B.
Hiromi
Hiromi is a Japanese jazz composer and virtuoso pianist renowned for her high-energy performances and fusion of jazz, classical, and rock influences.
-
C.
Hiroyuki
Hiroyuki is a Japanese given name commonly used for men, associated with various notable figures in entertainment, technology, and other fields.
-
D.
Hiroki
Hiroki is a Japanese given name commonly used for males, often associated with meanings like "vast," "great," or "abundant joy" depending on the kanji used.
-
E.
Hiroto
Hiroto is a masculine Japanese given name commonly associated with meanings like “large,” “great,” or “ocean,” depending on the kanji used.
- 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_69e0b50192308190a284fcc89dd23a49 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc41d57881908b9ab17d1844a8d0 |
completed | April 21, 2026, 4:25 a.m. |
Created at: April 16, 2026, 1:53 p.m.