Triple

T16596591
Position Surface form Disambiguated ID Type / Status
Subject Sir William Heseltine E403222 entity
Predicate honorificSuffix P341 FINISHED
Object AO E503433 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: AO | Statement: [Sir William Heseltine, honorificSuffix, AO]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: AO
Context triple: [Sir William Heseltine, honorificSuffix, AO]
  • A. AO
    AO is the two-letter ISO 3166-1 alpha-2 country code representing Angola in international standards and systems.
  • B. AO
    AO is the commonly used abbreviation for the Administrative Office of the United States Courts, the federal agency that provides administrative support to the U.S. federal judiciary.
  • C. AO
    AO is a UK-based online electricals retailer known for selling appliances and consumer electronics through its e-commerce platform and associated services.
  • D. AO chosen
    AO is the post-nominal abbreviation used to denote an individual appointed as an Officer of the Order of Australia, one of the nation’s highest civilian honours.
  • E. AO
    AO is the regional vehicle registration code used on license plates for vehicles registered in the Khust area of Ukraine.
  • 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_69d883880d0c81908b5fcd454e767b60 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e35d723c508190b5afbda5eec5abea completed April 18, 2026, 10:31 a.m.
NED1 Entity disambiguation (via context triple) batch_6a00759fe6ec81908c5321dcba558269 completed May 10, 2026, 12:10 p.m.
Created at: April 10, 2026, 5:16 a.m.