Triple

T7837631
Position Surface form Disambiguated ID Type / Status
Subject Regional Command North E181725 entity
Predicate instanceOf P0 FINISHED
Object ISAF regional command C22996 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: ISAF regional command
Context triple: [Regional Command North, instanceOf, ISAF regional command]
  • A. maritime confederation
    A maritime confederation is a loose alliance of seafaring states or cities that cooperate to control trade routes, naval defense, and maritime law while retaining their political independence.
  • B. maritime jurisdictional office
    A maritime jurisdictional office is a governmental or regulatory entity responsible for overseeing, enforcing, and administering laws, regulations, and policies within a defined maritime area or coastal zone.
  • C. maritime navigation authority
    A maritime navigation authority is an organization responsible for regulating, managing, and ensuring the safety and efficiency of vessel movements and navigational systems within designated waters.
  • D. NATO rapid reaction corps headquarters
    The NATO Rapid Reaction Corps Headquarters is a high-readiness, multinational command element responsible for planning, coordinating, and directing rapid deployment and operations of NATO land forces in crisis or conflict.
  • E. Japan Maritime Self-Defense Force district
    A Japan Maritime Self-Defense Force district is a regional naval command area responsible for organizing, administering, and supporting JMSDF units and operations within its designated geographic zone.
  • F. None of above. chosen

Provenance (1 batch)

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_69ca8284a25c8190a1a20afad30da792 completed March 30, 2026, 2:02 p.m.
Created at: March 30, 2026, 4:46 p.m.