Triple
T16093199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nova Sintra |
E390411
|
entity |
| Predicate | hasNearbySettlement |
P4647
|
FINISHED |
| Object | Furna |
E687579
|
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: Furna | Statement: [Nova Sintra, hasNearbySettlement, Furna]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Furna Context triple: [Nova Sintra, hasNearbySettlement, Furna]
-
A.
Furna
chosen
Furna is a coastal settlement on the Cape Verdean island of Brava that serves as its main maritime gateway and ferry port.
-
B.
Furna
Furna is a small Swiss mountain municipality located in the canton of Graubünden.
-
C.
Achada Furna
Achada Furna is a small village located on the island of Fogo in Cape Verde, known for its proximity to the island’s active volcano and its agricultural surroundings.
-
D.
Furnas Valley
Furnas Valley is a geothermal valley on São Miguel Island in the Azores, known for its hot springs, volcanic calderas, and lush, scenic landscapes.
-
E.
Aitna
Aitna is a primordial Greek mountain deity associated with Mount Etna and the volcanic forces of the earth.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1858ed09881909bde122971d95753 |
completed | April 17, 2026, 12:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffeb973c88819091fe284420088e7e |
completed | May 10, 2026, 2:21 a.m. |
Created at: April 10, 2026, 4:59 a.m.