Triple

T15610222
Position Surface form Disambiguated ID Type / Status
Subject Eastnor Castle E375268 entity
Predicate hasDefensiveAppearance P119428 FINISHED
Object battlements 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: battlements | Statement: [Eastnor Castle, hasDefensiveAppearance, battlements]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDefensiveAppearance
Context triple: [Eastnor Castle, hasDefensiveAppearance, battlements]
  • A. hasDefensiveWork
    Indicates that an entity possesses or is associated with a work focused on defense or protective functions.
  • B. hasDefensivePositions
    Indicates that an entity possesses or controls locations, structures, or arrangements specifically organized for defense against potential threats or attacks.
  • C. hasDefensivePurpose
    Indicates that something exists or is designed with the primary goal of protection, defense, or safeguarding against threats or harm.
  • D. hasDefenseStrategy
    Indicates that an entity employs or is associated with a particular plan or set of measures designed to protect against threats or attacks.
  • E. canBeDefendedIn
    Indicates that something (such as a claim, action, or position) is capable of being justified or supported within a specified context, forum, or framework.
  • 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_69d85ccf2794819096cda4cbcb02d478 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04e8024948190a6c711f2e5c2aac4 completed April 16, 2026, 2:50 a.m.
PD Predicate disambiguation batch_69deda844af081909e658ebc9d9b403d completed April 15, 2026, 12:23 a.m.
PDg Predicate description generation batch_69dff7f05f708190850f1d8782e132b0 completed April 15, 2026, 8:41 p.m.
Created at: April 10, 2026, 4:13 a.m.