Triple

T5365882
Position Surface form Disambiguated ID Type / Status
Subject Regnum Defende E103127 entity
Predicate hasGrammaticalMood P34383 FINISHED
Object imperative 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: imperative | Statement: [Regnum Defende, hasGrammaticalMood, imperative]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasGrammaticalMood
Context triple: [Regnum Defende, hasGrammaticalMood, imperative]
  • A. grammaticalMood chosen
    Indicates the grammatical mood used in an utterance, specifying the speaker’s attitude toward the action or state (such as indicative, imperative, or subjunctive).
  • B. grammaticalForm
    Indicates the specific grammatical structure or morphological form that an expression or word takes in a given linguistic context.
  • C. hasTense
    Indicates that an action, event, or state is associated with a specific grammatical tense (such as past, present, or future).
  • D. hasTenseAspect
    Indicates that a verb or clause is associated with a specific grammatical tense and aspect configuration.
  • E. hasVerbAspect
    Indicates that a verb or verbal expression is associated with a particular grammatical aspect (such as perfective, imperfective, or progressive) describing the temporal structure of the action or state.
  • 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_69bd43daa3e4819090b59d127db70e57 completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd8682d18c8190bbb35cc75c8a7c12 completed March 20, 2026, 5:40 p.m.
PD Predicate disambiguation batch_69bd845f41f88190b75b8b64b9e41862 completed March 20, 2026, 5:31 p.m.
Created at: March 20, 2026, 2:02 p.m.