Triple

T36039695
Position Surface form Disambiguated ID Type / Status
Subject NATO OF-9 E1042504 entity
Predicate isStandardizedAcross P184501 FINISHED
Object NATO member armed forces 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: NATO member armed forces | Statement: [NATO OF-9, isStandardizedAcross, NATO member armed forces]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isStandardizedAcross
Context triple: [NATO OF-9, isStandardizedAcross, NATO member armed forces]
  • A. isLessStandardizedThan
    Indicates that one entity follows fewer or less rigid standards, norms, or formalized procedures than another entity.
  • B. isStandardizationTargetOf
    Indicates that an entity is the object or subject being standardized within a standardization process, activity, or initiative.
  • C. standardizedBy
    Indicates that one entity defines, regulates, or formalizes the standards or specifications by which another entity is created, measured, or operated.
  • D. standardizedIn
    Indicates that something has been formally defined, regulated, or made uniform within a particular standard, framework, or jurisdiction.
  • E. isPartOfStandardizationSystem
    Indicates that something belongs to, or is included within, a defined standardization framework, scheme, or system.
  • 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_69f76e2d7e8c8190bac4e90734566799 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7b35e32d481909ef0220e6f6ff4a8 completed May 3, 2026, 8:43 p.m.
PD Predicate disambiguation batch_69f7b1bad2e88190963ab4ee5d4f2038 completed May 3, 2026, 8:36 p.m.
PDg Predicate description generation batch_69f7b2c66054819083897e25edb65ba7 completed May 3, 2026, 8:40 p.m.
Created at: May 3, 2026, 4:07 p.m.