Triple

T32541571
Position Surface form Disambiguated ID Type / Status
Subject Archaeological Site of Exceptional Importance E831725 entity
Predicate categoryWithinLaw P76736 FINISHED
Object exceptional importance 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: exceptional importance | Statement: [Archaeological Site of Exceptional Importance, categoryWithinLaw, exceptional importance]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: categoryWithinLaw
Context triple: [Archaeological Site of Exceptional Importance, categoryWithinLaw, exceptional importance]
  • A. branchOfLaw
    Indicates a relationship where one legal field or discipline is a subdivision or specialized area within a broader body of law.
  • B. juridicalCategory chosen
    Indicates the legal classification or status under which an entity or relationship is formally recognized in a juridical system.
  • C. typeOfLaw
    Indicates that one entity is a specific category or kind of law to which the other entity pertains.
  • D. subjectOfLaw
    Indicates that a law, legal document, or legal provision is about, concerns, or applies to the referenced subject.
  • E. legalMatters
    Indicates that one entity is involved with, concerned about, or responsible for legal issues, processes, or obligations related to another entity or context.
  • 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_69f34925fd08819084cfe4ec566cb704 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6c8159edc8190b1c87015e0c820e8 completed May 3, 2026, 3:59 a.m.
PD Predicate disambiguation batch_69f6c3f42fbc8190a06eb1044c9e6094 completed May 3, 2026, 3:41 a.m.
Created at: May 1, 2026, 1:02 a.m.