Triple

T19982821
Position Surface form Disambiguated ID Type / Status
Subject George Banks E493858 entity
Predicate familyName P18 FINISHED
Object Banks NE NERFINISHED

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: Banks | Statement: [George Banks, familyName, Banks]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Banks
Context triple: [George Banks, familyName, Banks]
  • A. Banks
    Banks is a small village in Lancashire, England, known for its rural character and proximity to the town of Tarleton.
  • B. Banks chosen
    Banks is a common English surname borne by numerous notable individuals across sports, politics, arts, and other fields.
  • C. Banks
    Banks is an Australian federal electoral division in New South Wales that includes suburbs such as Hurstville in Sydney’s south.
  • D. Banks
    Banks are financial institutions that accept deposits, provide loans, and offer a range of financial services to individuals, businesses, and governments, playing a central role in the global economy and financial system.
  • E. Banks
    Banks is a residential suburb in the Tuggeranong district of Canberra, Australian Capital Territory.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69da626a67648190af9653832a3aeced completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e65d14c3c08190b1ba8f4da08a4ccf completed April 20, 2026, 5:06 p.m.
Created at: April 11, 2026, 3:28 p.m.