Triple

T3484450
Position Surface form Disambiguated ID Type / Status
Subject Palazzo Madama E73573 entity
Predicate heritageLayer P41906 FINISHED
Object Roman city gate remains 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: Roman city gate remains | Statement: [Palazzo Madama, heritageLayer, Roman city gate remains]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: heritageLayer
Context triple: [Palazzo Madama, heritageLayer, Roman city gate remains]
  • A. heritageComponent
    Indicates that one entity forms a constituent or contributing part of another entity’s cultural or historical heritage.
  • B. heritageField
    Indicates that there is an association between an entity and a specific field, domain, or area related to cultural or historical heritage.
  • C. heritageFunction
    Indicates the role, use, or purpose that a heritage asset or element serves within its cultural, historical, or social context.
  • D. heritageVisibleIn chosen
    Indicates that a piece of heritage (e.g., cultural, historical, or architectural) is observable or perceptible in a given entity, such as a place, object, or practice.
  • E. heritageReference
    Indicates that one entity serves as a cultural, historical, or heritage-related reference or source for another entity.
  • 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_69ad85b3c9b08190857cae74c7f36da9 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adbb795db88190805b26d9774fdb73 completed March 8, 2026, 6:10 p.m.
PD Predicate disambiguation batch_69adae0935ac8190bfa8a8bd3dcd3301 completed March 8, 2026, 5:12 p.m.
Created at: March 8, 2026, 3:17 p.m.