Triple
T18284755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peak of Fire |
E437953
|
entity |
| Predicate | locatedOnIsland |
P970
|
FINISHED |
| Object | Fogo |
—
|
NE NERFINISHED |
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: Fogo | Statement: [Peak of Fire, locatedOnIsland, Fogo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fogo Context triple: [Peak of Fire, locatedOnIsland, Fogo]
-
A.
Fogo
chosen
Fogo is a volcanic island in Cape Verde known for its active stratovolcano Pico do Fogo and dramatic mountainous landscapes.
-
B.
Queimados
Queimados is a municipality in the state of Rio de Janeiro, Brazil, situated within the metropolitan area of the city of Rio de Janeiro.
-
C.
Buruanga
Buruanga is a coastal municipality in the province of Aklan in the Philippines, known for its scenic beaches and proximity to the tourist island of Boracay.
-
D.
Veiao
Veiao is an alternative name for the Chinese surname and given name "Yao," commonly used in certain transliterations or dialectal forms.
-
E.
Fuego
Fuego is a given name of Spanish origin meaning “fire,” used both as a first and middle name.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e500f913d48190b41a1e37ca05e8b1 |
completed | April 19, 2026, 4:21 p.m. |
Created at: April 10, 2026, 10:35 a.m.