Triple

T3855222
Position Surface form Disambiguated ID Type / Status
Subject 30 St Mary Axe E89996 entity
Predicate developer P73 FINISHED
Object Swiss Re E159943 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: Swiss Re | Statement: [30 St Mary Axe, developer, Swiss Re]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Swiss Re
Context triple: [30 St Mary Axe, developer, Swiss Re]
  • A. Swiss Re chosen
    Swiss Re is a leading global reinsurance company headquartered in Zurich, Switzerland, providing risk transfer and insurance solutions worldwide.
  • B. Munich Re
    Munich Re is a leading global reinsurance company based in Germany, known for providing risk management and insurance solutions worldwide.
  • C. Allianz
    Allianz is a leading global financial services company, best known as one of the world’s largest insurance and asset management providers.
  • D. Berkshire Hathaway Reinsurance Group
    Berkshire Hathaway Reinsurance Group is a major division of Berkshire Hathaway that provides large-scale reinsurance solutions across a wide range of insurance lines globally.
  • E. Aon Corporation
    Aon Corporation is a global professional services firm specializing in risk management, insurance brokerage, and human capital consulting.
  • 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_69aed95b3c088190a8f85d19e6070599 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aeec05ec4c8190bd5e5463163712dc completed March 9, 2026, 3:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5041f40f88190883339db0950026a completed March 14, 2026, 6:45 a.m.
Created at: March 9, 2026, 3:19 p.m.