Triple

T35517260
Position Surface form Disambiguated ID Type / Status
Subject Action of 15 May 1917 E1026451 entity
Predicate AustroHungarianFlagship P32468 FINISHED
Object SMS Novara 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: SMS Novara | Statement: [Action of 15 May 1917, AustroHungarianFlagship, SMS Novara]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: AustroHungarianFlagship
Context triple: [Action of 15 May 1917, AustroHungarianFlagship, SMS Novara]
  • A. AustrianFleetOutcome
    Indicates the result or consequence experienced by the Austrian fleet in a particular engagement or context.
  • B. involvedUnitAustriaHungary
    Indicates that the unit or force specified was involved on behalf of Austria-Hungary in the referenced event or conflict.
  • C. monarchOfAustriaDuringWar
    Indicates that a person held the position of monarch of Austria during a specified war or military conflict.
  • D. isWarEnsignOf chosen
    Indicates that one entity is the war ensign (a specific military or wartime flag) representing or belonging to another entity.
  • E. countryDuringAustriaHungaryPeriod
    Indicates that an entity functioned as a country or territorial unit during the historical period when Austria-Hungary existed.
  • 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_69f76dfe78b081908e2b14cb88dd8c00 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f79a54aa3c8190b2bb5d790b2d42d4 completed May 3, 2026, 6:56 p.m.
PD Predicate disambiguation batch_69f7961970408190b669cc556e30a608 completed May 3, 2026, 6:38 p.m.
Created at: May 3, 2026, 4:04 p.m.