Triple

T26954962
Position Surface form Disambiguated ID Type / Status
Subject Royal Sussex Regiment E678874 entity
Predicate raisedAdditionalBattalionsDuring P161372 FINISHED
Object Second World War NE NERFINISHED

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: Second World War | Statement: [Royal Sussex Regiment, raisedAdditionalBattalionsDuring, Second World War]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: raisedAdditionalBattalionsDuring
Context triple: [Royal Sussex Regiment, raisedAdditionalBattalionsDuring, Second World War]
  • A. raisedAdditionalBattalionsDuring chosen
    Indicates that an entity formed or mobilized extra military battalions during a specified time period or event.
  • B. raisedRegiment
    Indicates that an entity organized, formed, or brought into existence a specific military regiment.
  • C. numberOfBattalions
    Indicates the quantitative relationship specifying how many battalions are associated with a given entity or context.
  • D. numberOfRegimentsInvolved
    Indicates the total count of regiments that participated in or were involved in a specified event or action.
  • E. commandedTroopsAt
    Indicates that a person held command authority over military forces at a specific location or during a particular operation.
  • 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_69eeeb4e75f08190b14fc91ca4a91488 completed April 27, 2026, 4:51 a.m.
NER Named-entity recognition batch_69f620e6c9b481908a6c2608a376086e completed May 2, 2026, 4:05 p.m.
PD Predicate disambiguation batch_69f61b3ee7b08190a0a1bc5d26b757aa completed May 2, 2026, 3:41 p.m.
Created at: April 27, 2026, 6:26 a.m.