Triple

T22888102
Position Surface form Disambiguated ID Type / Status
Subject River Lune estuary E567659 entity
Predicate near P350 FINISHED
Object Lancaster 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: Lancaster | Statement: [River Lune estuary, near, Lancaster]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lancaster
Context triple: [River Lune estuary, near, Lancaster]
  • A. Lancaster
    The Lancaster is a British four-engined World War II heavy bomber renowned for its major role in night bombing campaigns and famous missions such as the "Dambusters" raid.
  • B. Lancaster
    Lancaster was the original settlement that later developed into the city of Lincoln, the capital of Nebraska.
  • C. Lancaster
    Lancaster was the original name of the city now known as Stockton in Missouri, a small Midwestern community in the United States.
  • D. Lancaster chosen
    Lancaster is a historic city in North West England known for its medieval castle, Georgian architecture, and role as the county town of Lancashire.
  • E. Lancaster
    Lancaster is a small community in eastern Ontario, Canada, located near the Quebec border along the St. Lawrence 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_69e2458a92ec81908fc1cd5f6407d2ab completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17fc2adb4819081bce7e6849ba31a completed April 29, 2026, 3:49 a.m.
Created at: April 17, 2026, 3:40 p.m.