Triple
T8010359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haʻapai |
E186472
|
entity |
| Predicate | hasVolcano |
P6356
|
FINISHED |
| Object | Kao |
E707329
|
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: Kao | Statement: [Haʻapai, hasVolcano, Kao]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kao Context triple: [Haʻapai, hasVolcano, Kao]
-
A.
Kao
Kao is a Chinese surname borne by numerous individuals, including notable figures in science, business, and the arts.
-
B.
Kao
chosen
Kao is a volcanic island in the Haʻapai group of Tonga, notable for being one of the country's highest and most prominent volcanic peaks.
-
C.
Michishio
Michishio was a Japanese Navy destroyer that served in World War II and was sunk during the Battle of Surigao Strait in 1944.
-
D.
Kiesen
Kiesen is a municipality in the canton of Bern, Switzerland, served by a station on the Bern–Thun railway line.
-
E.
Kachidoki
Kachidoki is a waterfront district in Tokyo’s Chūō ward known for its high-rise residential towers, proximity to the Sumida River, and convenient access to central Tokyo.
- 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_69ca82abaffc8190ab8af79cdbc31ab3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3d70caf8819090a9f98025470c0d |
completed | March 31, 2026, 3:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc63c1f76881909ad6d7777090f2e2 |
completed | April 1, 2026, 12:16 a.m. |
Created at: March 30, 2026, 5:19 p.m.