Triple
T15712459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hina |
E380872
|
entity |
| Predicate | hasVariantName |
P457
|
FINISHED |
| Object | Hina-uri |
E380872
|
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: Hina-uri | Statement: [Hina, hasVariantName, Hina-uri]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hina-uri Context triple: [Hina, hasVariantName, Hina-uri]
-
A.
Hina
chosen
Hina is a prominent figure in Polynesian mythology, often depicted as a goddess associated with the moon, femininity, and skilled crafts.
-
B.
Hyeonreung
Hyeonreung is a royal tomb from Korea’s Joseon Dynasty, notable as one of the UNESCO-listed burial sites of its kings and queens.
-
C.
Maeng-hee
Maeng-hee is a Korean given name, notably borne by individuals such as businessman Lee Maeng-hee.
-
D.
Sojin
Sojin is a given name, often used in East Asian cultures, that can refer to various individuals in entertainment, arts, and other fields.
-
E.
Asahi-hime
Asahi-hime was a Japanese noblewoman of the late Sengoku period, known for her politically significant marriage into the Tokugawa clan that helped secure alliances during Japan’s unification.
- 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_69d86d9bf930819082b30cf6d169297c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04f8f5d6081908243fa59b46b7c76 |
completed | April 16, 2026, 2:55 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff757f571881908015fe68df2a5e69 |
completed | May 9, 2026, 5:57 p.m. |
Created at: April 10, 2026, 4:45 a.m.