Triple

T7260936
Position Surface form Disambiguated ID Type / Status
Subject Nomans Land Island E159648 entity
Predicate reasonForRestrictedAccess P9584 FINISHED
Object unexploded ordnance 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: unexploded ordnance | Statement: [Nomans Land Island, reasonForRestrictedAccess, unexploded ordnance]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reasonForRestrictedAccess
Context triple: [Nomans Land Island, reasonForRestrictedAccess, unexploded ordnance]
  • A. accessRestrictedTo
    Indicates that access to a resource, location, or information is limited exclusively to a specified entity or group under defined conditions.
  • B. accessRestriction chosen
    Indicates a limitation or control placed on who or what can access a particular resource, location, or information.
  • C. protectionReason
    Indicates the justification or cause for which protection is provided or required in the relationship between entities.
  • D. reasonForPerformanceLimitation
    Indicates that one factor serves as the cause or explanation for why a performance limitation occurs.
  • E. hasPublicAccessRestrictions
    Indicates that there are specific limitations or conditions governing public access to the associated resource or 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_69c68838f9948190875fd60b2351230c completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6eb088dac8190b353f6ea3d686025 completed March 27, 2026, 8:39 p.m.
PD Predicate disambiguation batch_69c6e76876608190ac4652bc7153302e completed March 27, 2026, 8:24 p.m.
Created at: March 27, 2026, 2:57 p.m.