Triple

T2378701
Position Surface form Disambiguated ID Type / Status
Subject Boé Declaration on Regional Security E46260 entity
Predicate includesSecurityDimension P3815 FINISHED
Object human security 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: human security | Statement: [Boé Declaration on Regional Security, includesSecurityDimension, human security]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: includesSecurityDimension
Context triple: [Boé Declaration on Regional Security, includesSecurityDimension, human security]
  • A. hasSecurityNotion
    Indicates that one entity possesses, defines, or is associated with a particular concept or notion of security in relation to another entity or context.
  • B. hasSecurityConsideration
    Indicates that there is a relevant security-related issue, risk, or precaution associated with the referenced entity.
  • C. securityAspect chosen
    Indicates a relationship where something pertains to, represents, or characterizes a particular aspect or dimension of security.
  • D. securityFeature
    Indicates that an entity provides, embodies, or is associated with a mechanism or property intended to enhance safety, protection, or defense against threats or vulnerabilities.
  • E. hasSecurityArchitecture
    Indicates that an entity is associated with or defined by a particular security architecture design or framework.
  • 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_69a88a1554a48190a0180682bcf099be completed March 4, 2026, 7:37 p.m.
NER Named-entity recognition batch_69abc7974aa481908799ef2f854d1c9d completed March 7, 2026, 6:37 a.m.
PD Predicate disambiguation batch_69abc59f73f08190924a36d7d475d8f4 completed March 7, 2026, 6:28 a.m.
Created at: March 4, 2026, 7:57 p.m.