Triple

T21411546
Position Surface form Disambiguated ID Type / Status
Subject Ripon Hornblower E528182 entity
Predicate safetyFunctionOrigin P4098 FINISHED
Object historical town security signal 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: historical town security signal | Statement: [Ripon Hornblower, safetyFunctionOrigin, historical town security signal]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: safetyFunctionOrigin
Context triple: [Ripon Hornblower, safetyFunctionOrigin, historical town security signal]
  • A. safetyFunction
    Indicates that one entity serves as a safety-related function or mechanism that protects, safeguards, or reduces risk for another entity or process.
  • B. originalFunction chosen
    Indicates that one entity serves as the initial or primary function from which another function or behavior is derived or defined.
  • C. classOrigin
    Indicates the original class or category from which an entity is derived, instantiated, or classified.
  • D. safetyContext
    Indicates the circumstances, conditions, or environment that affect how safe an action, object, or situation is.
  • E. originProtectedStatus
    Indicates that an entity’s original source or location is subject to protection, restriction, or special safeguarding status.
  • 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_69e0c454c248819093425d1099101c09 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69e8b1fe2cd08190bfaf28daae4f5233 completed April 22, 2026, 11:33 a.m.
PD Predicate disambiguation batch_69e61633f8208190a2a849457c4e4198 completed April 20, 2026, 12:04 p.m.
Created at: April 16, 2026, 5:43 p.m.