Triple
T22899713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time Control |
E568275
|
entity |
| Predicate | artist |
P184
|
FINISHED |
| Object | Hiromi |
—
|
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: Hiromi | Statement: [Time Control, artist, Hiromi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hiromi Context triple: [Time Control, artist, Hiromi]
-
A.
Hiromi
chosen
Hiromi is a Japanese jazz composer and virtuoso pianist renowned for her high-energy performances and fusion of jazz, classical, and rock influences.
-
B.
Hirom
Hirom is a variant form of the name Hiram, which is of Hebrew origin and historically associated with biblical and ancient Near Eastern figures.
-
C.
Harumi
Harumi is a waterfront district in Tokyo’s Chūō ward known for its high-rise residential towers and role in the Tokyo 2020 Olympic and Paralympic Village.
-
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.
Hitoshi
Hitoshi is a Japanese given name commonly used for males.
- 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_69e2458c23ec81908fa2570692c6614f |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f180155b1c8190a83eb6ec45387a1a |
completed | April 29, 2026, 3:50 a.m. |
Created at: April 17, 2026, 3:41 p.m.