Triple

T26235793
Position Surface form Disambiguated ID Type / Status
Subject Commendation for Brave Conduct E656160 entity
Predicate scopeOfActsRecognised P160384 FINISHED
Object non-warlike bravery 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: non-warlike bravery | Statement: [Commendation for Brave Conduct, scopeOfActsRecognised, non-warlike bravery]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: scopeOfActsRecognised
Context triple: [Commendation for Brave Conduct, scopeOfActsRecognised, non-warlike bravery]
  • A. scopeOfUse
    Indicates the range, context, or conditions under which something is intended, allowed, or applicable to be used.
  • B. rightsRecognizedIn
    Indicates that certain rights are formally acknowledged or upheld within a specified context, such as a legal system, jurisdiction, or document.
  • C. legalScope
    Indicates the range, boundaries, or extent of authority, applicability, or effect that something has under a particular legal framework or rule.
  • D. hasRegulationScope
    Indicates that a regulation applies to, or governs, a specified scope, domain, or area of relevance.
  • E. scopeOfServiceRecognized
    Indicates that the extent or range of services provided has been formally acknowledged or accepted.
  • 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_69ee5b4b8b408190993da38c0067cc8d completed April 26, 2026, 6:36 p.m.
NER Named-entity recognition batch_69f60d8ab3b481908e7feeda0f8c47fa completed May 2, 2026, 2:43 p.m.
PD Predicate disambiguation batch_69f5f7fd90fc81909055b211368f9139 completed May 2, 2026, 1:11 p.m.
PDg Predicate description generation batch_69f600be0de88190989611e952b03117 completed May 2, 2026, 1:48 p.m.
Created at: April 26, 2026, 9:01 p.m.