Triple

T34752902
Position Surface form Disambiguated ID Type / Status
Subject Alseno E1001831 entity
Predicate hasRuralHeritage P181574 FINISHED
Object true 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: true | Statement: [Alseno, hasRuralHeritage, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRuralHeritage
Context triple: [Alseno, hasRuralHeritage, true]
  • A. hasHeritageValueFor
    Indicates that something possesses cultural, historical, or heritage significance for a particular entity or community.
  • B. hasHeritage
    Indicates that an entity possesses or is associated with a particular cultural, ethnic, or ancestral background.
  • C. hasHeritageFeature
    Indicates that an entity possesses or includes a feature recognized as part of cultural, historical, or natural heritage.
  • D. hasHeritageUse
    Indicates that something is used, managed, or valued in a way that relates to cultural, historical, or natural heritage.
  • E. hasHeritageElements
    Indicates that something contains or includes elements that are part of a cultural, historical, or natural heritage.
  • F. None of above. chosen

Provenance (4 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_69f76db0fb30819096709d43f9a1f45f completed May 3, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f77ffa6b68819090257fed3802c239 completed May 3, 2026, 5:03 p.m.
PD Predicate disambiguation batch_69f7795978c481909e152cd1bd02dd07 completed May 3, 2026, 4:35 p.m.
PDg Predicate description generation batch_69f77ff804f08190b431a31e6179ace4 completed May 3, 2026, 5:03 p.m.
Created at: May 3, 2026, 3:59 p.m.