Triple

T7001637
Position Surface form Disambiguated ID Type / Status
Subject Helvetii E162350 entity
Predicate locatedIn P40 FINISHED
Object Helvetia E31683 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: Helvetia | Statement: [Helvetii, locatedIn, Helvetia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Helvetia
Context triple: [Helvetii, locatedIn, Helvetia]
  • A. Helvetia chosen
    Helvetia is the female national personification of Switzerland, symbolizing the Swiss Confederation and its unity, independence, and identity.
  • B. Swissmint
    Swissmint is the official mint of Switzerland responsible for producing the country’s coins and other numismatic products.
  • C. Helvetia General Insurance Company
    Helvetia General Insurance Company is a Swiss insurance firm known for its role in the origins of Swiss Re, one of the world’s leading reinsurance companies.
  • D. Berner
    A Berner is a resident or native of the Swiss city of Bern.
  • E. Bernex
    Bernex is a municipality in western Switzerland located near the city of Geneva, known for its semi-rural character and surrounding vineyards.
  • 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_69c68857ffc08190857dc62cd5253777 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6dc0f8830819091f4356296234713 completed March 27, 2026, 7:35 p.m.
NED1 Entity disambiguation (via context triple) batch_69c76a310eb08190a0fc1de2814aea08 completed March 28, 2026, 5:42 a.m.
Created at: March 27, 2026, 2:33 p.m.