Triple

T1848900
Position Surface form Disambiguated ID Type / Status
Subject Army Reserve E41346 entity
Predicate mobilization P34132 FINISHED
Object can be called up in case of crisis 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: can be called up in case of crisis | Statement: [Army Reserve, mobilization, can be called up in case of crisis]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mobilization
Context triple: [Army Reserve, mobilization, can be called up in case of crisis]
  • A. mobilizationMethod
    Indicates the method or process by which resources, people, or assets are organized and activated for a particular purpose or operation.
  • B. mobilizationCentre
    Indicates a location where resources, personnel, or equipment are gathered and organized in preparation for deployment or coordinated action.
  • C. demobilization
    Indicates the process by which armed forces or combatants are formally released from military service and military structures are reduced or disbanded.
  • D. movementIn
    Indicates a relationship where an entity moves within, into, or inside a specified area, space, or container.
  • E. managedAct
    Indicates that one entity oversaw, directed, or was responsible for carrying out a particular action or activity.
  • F. None of above. chosen

Provenance (4 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_69a88648cd44819093303206d96d76ad completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69abb32d35508190bf1c487dffbecaf0 completed March 7, 2026, 5:10 a.m.
PD Predicate disambiguation batch_69abafdca6d8819083c66f3a29fd9fd1 completed March 7, 2026, 4:55 a.m.
PDg Predicate description generation batch_69abb32a8d548190a231c7c2ce276a5e completed March 7, 2026, 5:10 a.m.
Created at: March 4, 2026, 7:33 p.m.