Triple

T34434264
Position Surface form Disambiguated ID Type / Status
Subject NATO Allied reporting name system E883909 entity
Predicate SAMNamingRule P172869 FINISHED
Object two‑part names with SA‑number plus word 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: two‑part names with SA‑number plus word | Statement: [NATO Allied reporting name system, SAMNamingRule, two‑part names with SA‑number plus word]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: SAMNamingRule
Context triple: [NATO Allied reporting name system, SAMNamingRule, two‑part names with SA‑number plus word]
  • A. namingAuthorityContext
    Indicates the authority or governing context under which an entity’s name is formally assigned or recognized.
  • B. nominalRule chosen
    Indicates that something functions as a naming or labeling rule that defines how a term, label, or category should be assigned or interpreted.
  • C. usesNamingSystem
    Indicates that one entity adopts or applies a particular naming system or convention to identify or label other entities.
  • D. hasRuleName
    Indicates that an entity is associated with a specific rule identified by a particular name.
  • E. hasNaming
    Indicates that one entity assigns, bears, or is associated with a specific name or designation provided by another 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_69f349c548d88190978e2a82502c03d0 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f71947ad88819082ab9d85dd493b01 completed May 3, 2026, 9:45 a.m.
PD Predicate disambiguation batch_69f71824431081908d9685d2462ea242 completed May 3, 2026, 9:40 a.m.
Created at: May 1, 2026, 2 a.m.