Triple
T15928650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kunanyi |
E386268
|
entity |
| Predicate | hasIndigenousName |
P1435
|
FINISHED |
| Object | kunanyi |
E386268
|
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: kunanyi | Statement: [Kunanyi, hasIndigenousName, kunanyi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: kunanyi Context triple: [Kunanyi, hasIndigenousName, kunanyi]
-
A.
Kunanyi
chosen
Kunanyi is the Indigenous Palawa name for the prominent mountain that overlooks Hobart in Tasmania, Australia.
-
B.
Kanyok
Kanyok is a Bantu language spoken primarily by the Kanyok people in the Democratic Republic of the Congo.
-
C.
Kunwinjku
Kunwinjku is an Aboriginal Australian language and cultural group traditionally associated with western Arnhem Land in the Northern Territory.
-
D.
Kurnalpi
Kurnalpi is a remote locality in Western Australia’s Goldfields region, historically associated with gold mining and now sparsely populated.
-
E.
Kutiyana
Kutiyana is a town in the Porbandar district of Gujarat, India, known historically as a local trading and administrative center.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e156a39abc8190927818f6e185033a |
completed | April 16, 2026, 9:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffb5b0833081909668c042234b5b75 |
completed | May 9, 2026, 10:31 p.m. |
Created at: April 10, 2026, 4:52 a.m.