Triple

T20109217
Position Surface form Disambiguated ID Type / Status
Subject Royal Navy ISR assets E490280 entity
Predicate includesSystemType P15304 FINISHED
Object command, control, communications, computers and intelligence systems 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: command, control, communications, computers and intelligence systems | Statement: [Royal Navy ISR assets, includesSystemType, command, control, communications, computers and intelligence systems]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: includesSystemType
Context triple: [Royal Navy ISR assets, includesSystemType, command, control, communications, computers and intelligence systems]
  • A. systemType chosen
    Indicates the classification or category of a system that an entity belongs to or operates as.
  • B. belongsToSystemType
    Indicates that one entity is classified under, or is a member of, a particular system type.
  • C. systemTypeOperated
    Indicates that an entity operates, controls, or runs a particular type of system.
  • D. supportedSystem
    Indicates that one entity provides compatibility, functionality, or operational support for another system.
  • E. limitedSystemType
    Indicates that the system is restricted to a specific subset or category of system types, rather than allowing all possible types.
  • 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_69da62636cc08190982cc71733a17b8d completed April 11, 2026, 3:01 p.m.
NER Named-entity recognition batch_69e666df1b148190a28ead2f7cce7aab completed April 20, 2026, 5:48 p.m.
PD Predicate disambiguation batch_69e54cf788188190a46cc49c9ce7617f completed April 19, 2026, 9:45 p.m.
Created at: April 11, 2026, 11:28 p.m.