Triple

T5295493
Position Surface form Disambiguated ID Type / Status
Subject Koepoort city gate E119842 entity
Predicate hasArchitecturalValue P10074 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: [Koepoort city gate, hasArchitecturalValue, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasArchitecturalValue
Context triple: [Koepoort city gate, hasArchitecturalValue, true]
  • A. hasArchitecturalSignificance chosen
    Indicates that something possesses notable architectural qualities, importance, or influence that make it worthy of special attention or recognition.
  • B. hasArchitecturalFeature
    Indicates that one entity possesses, includes, or is characterized by a specific architectural feature or element.
  • C. hasArchaeologicalValue
    Indicates that something possesses significance or worth in the study, preservation, or interpretation of past human activity through material remains.
  • D. hasHeritageValueFor
    Indicates that something possesses cultural, historical, or heritage significance for a particular entity or community.
  • E. heritageValue
    Indicates that something possesses cultural, historical, or traditional significance that is valued and preserved as heritage.
  • 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_69bd446f22b88190b6a47fb91c68a3e7 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd8682d18c8190bbb35cc75c8a7c12 completed March 20, 2026, 5:40 p.m.
PD Predicate disambiguation batch_69bd844dfdac819086efedd1cbebff84 completed March 20, 2026, 5:30 p.m.
Created at: March 20, 2026, 1:52 p.m.