Triple

T21422875
Position Surface form Disambiguated ID Type / Status
Subject Fonte da Vila E528478 entity
Predicate hasTouristInformationSignage P51898 FINISHED
Object yes 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: yes | Statement: [Fonte da Vila, hasTouristInformationSignage, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTouristInformationSignage
Context triple: [Fonte da Vila, hasTouristInformationSignage, yes]
  • A. hasTouristSignage chosen
    Indicates that there is official signage present to guide or inform tourists about a place, route, or attraction.
  • B. hasTrailheadSignage
    Indicates that a trailhead is equipped with signage providing information or guidance to users.
  • C. hasTouristInfrastructure
    Indicates that a place is equipped with facilities and services designed to support and accommodate tourists.
  • D. hasSignageIn
    Indicates that appropriate signs or signage for an entity are present or installed within a specified location or area.
  • E. hasParkServiceSign
    Indicates that an entity features or is marked by an official park service sign.
  • 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_69e0c455f3688190810bc96365791b0f completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ee8139ce848190b812d6d07f1bdef8 completed April 26, 2026, 9:18 p.m.
PD Predicate disambiguation batch_69e61639ee288190889ffd500d1260f6 completed April 20, 2026, 12:04 p.m.
Created at: April 16, 2026, 5:48 p.m.