Triple

T17641293
Position Surface form Disambiguated ID Type / Status
Subject Test Way E429234 entity
Predicate passesNear P416 FINISHED
Object Romsey 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: Romsey | Statement: [Test Way, passesNear, Romsey]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Romsey
Context triple: [Test Way, passesNear, Romsey]
  • A. Romsey chosen
    Romsey is a historic market town in Hampshire, England, known for its medieval abbey and riverside setting.
  • B. Romsey and Wellow
    Romsey and Wellow is a Church of England benefice in Hampshire that groups together several local parishes, including St Margaret’s Church in East Wellow, under shared clergy and administration.
  • C. Romsey Abbey
    Romsey Abbey is a historic former Benedictine nunnery and parish church in Hampshire, England, noted for its impressive Norman architecture and royal connections.
  • D. Amesbury
    Amesbury is a historic town in Wiltshire, England, best known for its proximity to the prehistoric monument of Stonehenge.
  • E. Amesbury
    Amesbury is a historic New England city in northeastern Massachusetts known for its early shipbuilding and industrial heritage along the Merrimack River.
  • 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_69d889e2c2608190b762e76d9b2262f1 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e46de645208190a40dcf443f8afd82 completed April 19, 2026, 5:53 a.m.
Created at: April 10, 2026, 6:03 a.m.