Triple

T4827244
Position Surface form Disambiguated ID Type / Status
Subject Office of Naval Reactors E107854 entity
Predicate hasProgramScope P397 FINISHED
Object research and development in naval nuclear propulsion 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: research and development in naval nuclear propulsion | Statement: [Office of Naval Reactors, hasProgramScope, research and development in naval nuclear propulsion]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasProgramScope
Context triple: [Office of Naval Reactors, hasProgramScope, research and development in naval nuclear propulsion]
  • A. hasScope chosen
    Indicates that one entity defines, limits, or encompasses the range, extent, or applicability within which another entity operates or is valid.
  • B. hasBroadcastScope
    Indicates that a broadcast is intended to reach a specified scope or range of recipients, areas, or contexts.
  • C. hasProgramElement
    Indicates that one entity contains, includes, or is associated with a specific program element (such as a function, class, module, or code component).
  • D. isGlobalScope
    Indicates that something exists or applies at the global scope, rather than being limited to a local or nested context.
  • E. hasProgramCode
    Indicates that an entity is associated with a specific program identifier or code used to reference or classify it within a system.
  • 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_69bd43fac8188190803f0327190621e4 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6ddd17d881909f7731ff2b460e83 completed March 20, 2026, 3:55 p.m.
PD Predicate disambiguation batch_69bd6c1fe130819087ae01309f96a0c8 completed March 20, 2026, 3:47 p.m.
Created at: March 20, 2026, 1:24 p.m.