Triple
T14870925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hankutchin |
E349739
|
entity |
| Predicate | hasEthnonym |
P1435
|
FINISHED |
| Object | Hankutchin |
E349739
|
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: Hankutchin | Statement: [Hankutchin, hasEthnonym, Hankutchin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hankutchin Context triple: [Hankutchin, hasEthnonym, Hankutchin]
-
A.
Hankutchin
chosen
Hankutchin is an alternative name for the Hän, an Athabaskan-speaking Indigenous people of the Yukon–Alaska border region.
-
B.
Hwangje
Hwangje is the Korean imperial title corresponding to the Chinese sovereign known as the Yellow Emperor (Huangdi).
-
C.
Colhoon
Colhoon is a surname variant associated with the Scottish Clan Colquhoun.
-
D.
Chinnaru
Chinnaru is a minor tributary river that feeds into the Noyyal River in the Indian state of Tamil Nadu.
-
E.
Honcharuk
Honcharuk is a Ukrainian surname most notably associated with Oleksiy Honcharuk, a former Prime Minister of Ukraine.
- 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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded57967748190a7c05ebb74aacb7c |
completed | April 15, 2026, 12:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe65129a588190bbad294b500f411f |
completed | May 8, 2026, 10:34 p.m. |
Created at: April 10, 2026, 1:55 a.m.