Triple

T10801490
Position Surface form Disambiguated ID Type / Status
Subject Aon plc E254847 entity
Predicate hasDivision P35 FINISHED
Object Aon Risk Solutions E48249 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: Aon Risk Solutions | Statement: [Aon plc, hasDivision, Aon Risk Solutions]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aon Risk Solutions
Context triple: [Aon plc, hasDivision, Aon Risk Solutions]
  • A. Aon Corporation chosen
    Aon Corporation is a global professional services firm specializing in risk management, insurance brokerage, and human capital consulting.
  • B. AIG
    AIG (American International Group) is a global insurance and financial services corporation known for its extensive property-casualty, life insurance, and retirement products.
  • C. Swiss Re
    Swiss Re is a leading global reinsurance company headquartered in Zurich, Switzerland, providing risk transfer and insurance solutions worldwide.
  • D. Munich Re
    Munich Re is a leading global reinsurance company based in Germany, known for providing risk management and insurance solutions worldwide.
  • E. Allianz
    Allianz is a leading global financial services company, best known as one of the world’s largest insurance and asset management providers.
  • 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_69d6aa61c15c8190a1839550c56e75e1 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d7336dedec819099bd302c5d213dba completed April 9, 2026, 5:04 a.m.
NED1 Entity disambiguation (via context triple) batch_69de566e7d408190946864e28c294075 completed April 14, 2026, 2:59 p.m.
Created at: April 8, 2026, 9:18 p.m.