Triple

T2566794
Position Surface form Disambiguated ID Type / Status
Subject Imperator E57368 entity
Predicate governingDomain P15563 FINISHED
Object military command 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: military command | Statement: [Imperator, governingDomain, military command]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: governingDomain
Context triple: [Imperator, governingDomain, military command]
  • A. regulatoryDomain
    Indicates that one entity defines or governs the rules, policies, or constraints under which another entity must operate.
  • B. governmentalDomain chosen
    Indicates that one entity functions as the governmental sphere, jurisdiction, or area of authority within which another entity operates or is regulated.
  • C. inputDomain
    Indicates that a function, process, or system accepts inputs belonging to a specified domain or set of allowable values.
  • D. partOfDomain
    Indicates that one entity belongs to, is included within, or is a constituent part of the scope or domain defined by another entity.
  • E. publicDomain
    Indicates that a work or resource is not protected by intellectual property rights and is freely available for anyone to use, copy, modify, and distribute without restriction.
  • 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_69ab4a4ef9008190a0e6d4422b9418b7 completed March 6, 2026, 9:42 p.m.
NER Named-entity recognition batch_69abd3602ed08190aad0f9c7ac577eb0 completed March 7, 2026, 7:27 a.m.
PD Predicate disambiguation batch_69abd0cc8d308190ae7aa32b8f5ae2e5 completed March 7, 2026, 7:16 a.m.
Created at: March 6, 2026, 9:48 p.m.