Triple

T8050490
Position Surface form Disambiguated ID Type / Status
Subject Gunnersbury E187659 entity
Predicate near P350 FINISHED
Object Acton E394114 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: Acton | Statement: [Gunnersbury, near, Acton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Acton
Context triple: [Gunnersbury, near, Acton]
  • A. Acton
    Acton is a suburban town in Middlesex County, Massachusetts, known for its residential communities, conservation land, and commuter access to Boston.
  • B. Acton
    Acton is an inner suburb of Canberra, Australia, known for housing major national institutions such as the Australian National University and several key cultural and research facilities.
  • C. Acton
    Acton is a village and civil parish located in the county of Suffolk in eastern England.
  • D. Acton chosen
    Acton is a largely residential and commercial district in the London Borough of Ealing, known for its diverse community and good transport links into central London.
  • E. Acton
    Acton is a small community within the town of Halton Hills in Ontario, Canada, historically known for its leather and tanning industry.
  • 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_69ca82b15e948190a62fd7af5218426a completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3f799d1481909c91039941af0e34 completed March 31, 2026, 3:28 a.m.
NED1 Entity disambiguation (via context triple) batch_69cc93cc0cec8190834e4c24f6d03a99 completed April 1, 2026, 3:41 a.m.
Created at: March 30, 2026, 5:24 p.m.