Triple

T20027916
Position Surface form Disambiguated ID Type / Status
Subject American Forces Network E495035 entity
Predicate regulatesContentWith P61102 FINISHED
Object Department of Defense policies 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: Department of Defense policies | Statement: [American Forces Network, regulatesContentWith, Department of Defense policies]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regulatesContentWith
Context triple: [American Forces Network, regulatesContentWith, Department of Defense policies]
  • A. regulatesContentBy
    Indicates that one entity controls, directs, or sets rules for the nature, form, or distribution of another entity’s content.
  • B. regulatesContentFor chosen
    Indicates that one entity controls, manages, or sets rules governing the content produced, shared, or accessed by another entity.
  • C. regulatesWith
    Indicates that one entity controls, modulates, or influences the activity, state, or behavior of another entity through some regulatory mechanism or interaction.
  • D. contentRestriction
    Indicates that access to or use of certain content is limited or controlled based on specified rules or conditions.
  • E. regulatesUse
    Indicates that one entity controls, governs, or sets rules for how another entity may be used.
  • 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_69da626bfd288190aa5d65098b6433ae completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e6628f67e081909b9e69dfbe2127ce completed April 20, 2026, 5:29 p.m.
PD Predicate disambiguation batch_69e54ce752748190a0a1ffddd0372271 completed April 19, 2026, 9:45 p.m.
Created at: April 11, 2026, 3:35 p.m.