Triple

T19164937
Position Surface form Disambiguated ID Type / Status
Subject Ilha do Maio E469154 entity
Predicate hasSettlement P1068 FINISHED
Object Figueira da Horta 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: Figueira da Horta | Statement: [Ilha do Maio, hasSettlement, Figueira da Horta]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Figueira da Horta
Context triple: [Ilha do Maio, hasSettlement, Figueira da Horta]
  • A. Figueira da Horta chosen
    Figueira da Horta is a small village located on the island of Maio in Cape Verde.
  • B. Figueira da Foz
    Figueira da Foz is a coastal Portuguese city at the mouth of the Mondego River, known for its wide sandy beaches and seaside tourism.
  • C. Armação de Pêra
    Armação de Pêra is a coastal resort town in Portugal’s Algarve region, known for its sandy beaches and tourism.
  • D. Porto-Campanhã
    Porto-Campanhã is the main railway station in Porto, Portugal, serving as a central hub for long-distance and regional train services across the country.
  • E. Odivelas
    Odivelas is a suburban city and municipality in the Lisbon metropolitan area of Portugal, known for its residential character and proximity to the capital.
  • 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_69d8dd09d5a081909ae43c286651ae5a completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5f15e2720819084b1707497db26a2 completed April 20, 2026, 9:26 a.m.
Created at: April 10, 2026, 12:06 p.m.