Triple
T15712457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hina |
E380872
|
entity |
| Predicate | hasVariantName |
P457
|
FINISHED |
| Object | Hina-i-ka-malama |
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-i-ka-malama | Statement: [Hina, hasVariantName, Hina-i-ka-malama]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hina-i-ka-malama Context triple: [Hina, hasVariantName, Hina-i-ka-malama]
-
A.
Hina-‘a
Hina-‘a is a variant name for Hina, a prominent goddess in Polynesian mythology often associated with the moon, creativity, and feminine power.
-
B.
Hina-te-iwaiwa
Hina-te-iwaiwa is a revered Māori goddess associated with weaving, childbirth, and the moon.
-
C.
Hina
chosen
Hina is a prominent figure in Polynesian mythology, often depicted as a goddess associated with the moon, femininity, and skilled crafts.
-
D.
Mahal
Mahal is a historic neighborhood in Nagpur, India, known as one of the city’s oldest and most culturally significant localities.
-
E.
Mahal
Mahal is a royal title historically used in the Mughal Empire to denote a queen or high-ranking consort in the imperial harem.
- 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_69ff82f22fc88190820ecb171041136d |
completed | May 9, 2026, 6:54 p.m. |
Created at: April 10, 2026, 4:45 a.m.