Triple

T18075387
Position Surface form Disambiguated ID Type / Status
Subject Special operations command E432540 entity
Predicate mayBeOrganizedAt P61844 FINISHED
Object national level 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: national level | Statement: [Special operations command, mayBeOrganizedAt, national level]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mayBeOrganizedAt
Context triple: [Special operations command, mayBeOrganizedAt, national level]
  • A. mayBeOrganizedBy
    Indicates that an event, activity, or entity has the possibility of being organized or arranged by a particular agent or organization, without asserting that this organization definitely occurs.
  • B. organisedFor
    Indicates that something has been arranged, structured, or coordinated specifically to serve, support, or benefit a particular entity or purpose.
  • C. organisedDuring
    Indicates that an organizing action or arrangement took place within the time span of a specified event or period.
  • D. organizedAt chosen
    Indicates that an event or activity was arranged, planned, or hosted at a specific location or venue.
  • E. oftenOrganizedBy
    Indicates that an event, activity, or process is frequently arranged, coordinated, or hosted by a particular agent or entity.
  • 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_69d8b9070cac81909fa9473fb1c3f1c7 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4d9f40c9881909294d538c026d486 completed April 19, 2026, 1:34 p.m.
PD Predicate disambiguation batch_69e3f90c652481908133a73106d78919 completed April 18, 2026, 9:35 p.m.
Created at: April 10, 2026, 10:26 a.m.