Triple

T36582748
Position Surface form Disambiguated ID Type / Status
Subject Battle of Vis (1866) E902437 entity
Predicate AustrianFlagship P9819 FINISHED
Object SMS Erzherzog Ferdinand Max 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 Erzherzog Ferdinand Max | Statement: [Battle of Vis (1866), AustrianFlagship, SMS Erzherzog Ferdinand Max]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: AustrianFlagship
Context triple: [Battle of Vis (1866), AustrianFlagship, SMS Erzherzog Ferdinand Max]
  • A. AustrianDesignation
    Indicates that an entity has an official designation, title, or status specifically within the Austrian context (e.g., by Austrian law, administration, or standards).
  • B. AustrianStrength
    Indicates a relationship where an entity possesses or exhibits strength specifically associated with Austria, such as Austrian power, influence, or capability.
  • C. AustrianObjective
    Indicates that an entity has an objective, goal, or purpose specifically associated with Austria or Austrian context.
  • D. flagshipFor chosen
    Indicates that one entity serves as the primary or leading representative example for another entity, often embodying its most important qualities or status.
  • E. involvedUnitAustrian
    Indicates that an Austrian military or organizational unit was involved as a participant in the referenced event or activity.
  • 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_69f76e64d8908190868473959a250b94 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7c371931c8190afb1d4dd5157f92c completed May 3, 2026, 9:51 p.m.
PD Predicate disambiguation batch_69f7c1baf25c8190a78dd54a400d2c50 completed May 3, 2026, 9:44 p.m.
Created at: May 3, 2026, 4:11 p.m.