Triple
T9149949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pomerape Volcano |
E219558
|
entity |
| Predicate | mapLabel |
P13793
|
FINISHED |
| Object | Pomerape |
E300969
|
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: Pomerape | Statement: [Pomerape Volcano, mapLabel, Pomerape]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pomerape Context triple: [Pomerape Volcano, mapLabel, Pomerape]
-
A.
Pomerape
chosen
Pomerape is a stratovolcano in the Andes Mountains on the border between Chile and Bolivia, known as part of the Nevados de Payachata volcanic group.
-
B.
Pacasmayo
Pacasmayo is a coastal city in northern Peru known for its long pier, surfing beaches, and colonial-era architecture.
-
C.
Pitalito
Pitalito is a major town and coffee-producing hub in southern Colombia, known as one of the country’s most important centers for high-quality coffee.
-
D.
Puyuma
Puyuma are an indigenous Austronesian ethnic group of southeastern Taiwan known for their distinct language, matrilineal social structure, and rich ceremonial traditions.
-
E.
Huambisa
Huambisa is an indigenous Jivaroan language spoken by the Huambisa people of the northern Peruvian Amazon.
- 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_69ca83e121dc81909912bd66953081c5 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca96908d88190a1d12517f6d1aece |
completed | April 1, 2026, 5:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0483cdd048190904260c44a5810cf |
completed | April 3, 2026, 11:07 p.m. |
Created at: March 30, 2026, 7:20 p.m.