Triple

T3614021
Position Surface form Disambiguated ID Type / Status
Subject Battle of Cape Spartivento E76556 entity
Predicate forceInvolved P14890 FINISHED
Object Force H E365710 NE 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: Force H | Statement: [Battle of Cape Spartivento, forceInvolved, Force H]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Force H
Context triple: [Battle of Cape Spartivento, forceInvolved, Force H]
  • A. Force H chosen
    Force H was a British Royal Navy task force based at Gibraltar during World War II, known for its key role in Mediterranean and Atlantic naval operations.
  • B. HF
    HF is the Faculty of Humanities at the University of Oslo, encompassing disciplines such as languages, history, culture, and philosophy.
  • C. E for Everyone
    E for Everyone is an ESRB content rating indicating that a video game is generally suitable for players of all ages.
  • D. HAF
    HAF is the commonly used abbreviation for the Hellenic Air Force, the air warfare branch of Greece’s armed forces.
  • E. Hfd
    Hfd is the official station code used to identify Hoofddorp railway station in the Dutch rail network.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ad85da0ba481908b3b48c69efe2b98 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc279f6948190b9655a4cf3e77d89 completed March 8, 2026, 6:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69b43316224081909372f1007becc663 completed March 13, 2026, 3:53 p.m.
Created at: March 8, 2026, 3:23 p.m.