Triple

T20902914
Position Surface form Disambiguated ID Type / Status
Subject Borger-Odoorn E514714 entity
Predicate hasPrehistoricMonuments P33395 FINISHED
Object dolmens 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: dolmens | Statement: [Borger-Odoorn, hasPrehistoricMonuments, dolmens]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPrehistoricMonuments
Context triple: [Borger-Odoorn, hasPrehistoricMonuments, dolmens]
  • A. hasHistoricSite
    Indicates that an entity possesses, contains, or is associated with a place recognized for its historical significance.
  • B. hasArchaeologicalFeature chosen
    Indicates that an entity possesses, contains, or is associated with a specific archaeological feature or structure.
  • C. hasArchaeologicalValue
    Indicates that something possesses significance or worth in the study, preservation, or interpretation of past human activity through material remains.
  • D. hasArchaeologicalMound
    Indicates that an entity possesses or contains an archaeological mound, i.e., a raised earthwork or mound of archaeological significance located on or within it.
  • E. hasScheduledMonument
    Indicates that an entity is associated with, or contains, a site or structure officially designated as a scheduled monument.
  • 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_69e0b4f8a1108190bce3d31331290ced completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6e8fd7e4481909088b7f74ba24549 completed April 21, 2026, 3:03 a.m.
PD Predicate disambiguation batch_69e5c9ac91108190a6700fcdf2f11890 completed April 20, 2026, 6:37 a.m.
Created at: April 16, 2026, 12:47 p.m.