Triple

T5756196
Position Surface form Disambiguated ID Type / Status
Subject Battle E126973 entity
Predicate locatedNear P294 FINISHED
Object Hastings E75945 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: Hastings | Statement: [Battle, locatedNear, Hastings]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hastings
Context triple: [Battle, locatedNear, Hastings]
  • A. Hastings chosen
    Hastings is a historic seaside town and popular coastal resort in East Sussex, England, best known for its association with the 1066 Battle of Hastings and its traditional fishing and tourism industries.
  • B. Hastings
    Hastings is a major urban center in the Hawke's Bay region of New Zealand's North Island, known for its agriculture, wineries, and Art Deco and Spanish Mission-style architecture.
  • C. Hastings
    Hastings is a surname most prominently associated with Reed Hastings, the co-founder and longtime CEO of Netflix.
  • D. Hastings
    Hastings is a coastal town on Victoria, Australia’s Mornington Peninsula known for its port facilities and access to Western Port Bay.
  • E. Richborough
    Richborough is a historic site in Kent, England, known for its significant Roman remains and its role as a key gateway to Roman Britain.
  • 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_69c00832aedc81909899801b141fa3b4 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c02906848c8190bf7b0d62f57c27fa completed March 22, 2026, 5:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0bf9968d881908ef4065d1d13b2b8 completed March 23, 2026, 4:20 a.m.
Created at: March 22, 2026, 3:49 p.m.