Triple

T18284494
Position Surface form Disambiguated ID Type / Status
Subject São Filipe E437946 entity
Predicate regionalPosition P80554 FINISHED
Object western part of Fogo Island LITERAL 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: western part of Fogo Island | Statement: [São Filipe, regionalPosition, western part of Fogo Island]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regionalPosition
Context triple: [São Filipe, regionalPosition, western part of Fogo Island]
  • A. hasRegionalPosition chosen
    Indicates that one entity holds a specific role, status, or placement within a defined geographic or regional context relative to another entity.
  • B. regionalOrientation
    Indicates how something is directed, aligned, or focused toward a particular geographic region or area.
  • C. regionalComponent
    Indicates that one entity functions as a sub-region or constituent part within the larger geographic or administrative area represented by the other entity.
  • D. regionalType
    Indicates the classification of a region according to its designated type or category within a broader geographic or administrative system.
  • E. isRegional
    Indicates that something pertains to, is characteristic of, or is limited to a specific geographic region or area.
  • F. None of above.

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_69d8b914530c8190b4474d862a2b2a1b completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e500f913d48190b41a1e37ca05e8b1 completed April 19, 2026, 4:21 p.m.
PD Predicate disambiguation batch_69e44fd81c788190b08c6be3b07a08c5 completed April 19, 2026, 3:45 a.m.
Created at: April 10, 2026, 10:35 a.m.