Triple

T7800558
Position Surface form Disambiguated ID Type / Status
Subject Brierfield E180418 entity
Predicate postTown P2711 FINISHED
Object NELSON E33729 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: NELSON | Statement: [Brierfield, postTown, NELSON]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: NELSON
Context triple: [Brierfield, postTown, NELSON]
  • A. Nelson chosen
    Nelson is a former mill town in Lancashire, England, known for its industrial heritage and location near the Pennine hills.
  • B. Nelson
    Nelson is a coastal city at the top of New Zealand’s South Island, known for its arts scene, sunny climate, and access to nearby national parks.
  • C. Nelson
    Nelson is a common English-language surname borne by numerous notable figures across politics, sports, entertainment, and academia.
  • D. Nelson
    Nelson is a masculine given name of English origin that has been borne by various notable figures in politics, sports, and the arts.
  • E. Nelson, New Zealand
    Nelson, New Zealand is a coastal city at the top of the South Island known for its sunny climate, arts scene, and access to nearby national parks and beaches.
  • 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_69ca827e50cc8190a92a733577184938 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cae98765c48190b325eee67bd663fc completed March 30, 2026, 9:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69cb5a24692c8190ade15140fd2b9499 completed March 31, 2026, 5:22 a.m.
Created at: March 30, 2026, 4:33 p.m.