Triple

T36582753
Position Surface form Disambiguated ID Type / Status
Subject Battle of Vis (1866) E902437 entity
Predicate AustrianIronclad P177076 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), AustrianIronclad, SMS Erzherzog Ferdinand Max]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: AustrianIronclad
Context triple: [Battle of Vis (1866), AustrianIronclad, SMS Erzherzog Ferdinand Max]
  • A. AustroHungarianShipInvolved
    Indicates that a ship belonging to or operated by the Austro-Hungarian Empire was involved in a specified event or interaction.
  • B. AustrianFleetOutcome
    Indicates the result or consequence experienced by the Austrian fleet in a particular engagement or context.
  • C. notableVictimShip
    Indicates that a ship is recognized as a particularly significant or noteworthy victim in a specific incident or context.
  • D. isWarshipOf chosen
    Indicates that a given warship belongs to, is operated by, or is part of the naval forces of a specified country or organization.
  • E. AdmiralGrafSpeeLaidUpAt
    Indicates that the ship Admiral Graf Spee was laid up, moored, or taken out of active service at a specific location.
  • 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_69f7c777e924819081a6634f549fe552 completed May 3, 2026, 10:08 p.m.
PD Predicate disambiguation batch_69f7c477a4d481908f52e55b6688f60c completed May 3, 2026, 9:56 p.m.
Created at: May 3, 2026, 4:11 p.m.