Triple

T21964975
Position Surface form Disambiguated ID Type / Status
Subject Hilsea E542434 entity
Predicate hasLandmark P105 FINISHED
Object Hilsea Lines 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: Hilsea Lines | Statement: [Hilsea, hasLandmark, Hilsea Lines]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hilsea Lines
Context triple: [Hilsea, hasLandmark, Hilsea Lines]
  • A. Hilsea Lines chosen
    Hilsea Lines is a historic line of defensive fortifications in Portsmouth, England, built to protect the northern landward approaches to Portsea Island.
  • B. Sheerness Line
    The Sheerness Line is a railway branch in Kent, England, connecting the town of Sittingbourne on the Chatham Main Line to the Isle of Sheppey, including the port town of Sheerness.
  • C. Jamaica Line
    The Jamaica Line is an elevated New York City Subway corridor in Brooklyn and Queens that carries services such as the M train.
  • D. Port Island Line
    The Port Island Line is an automated guideway transit system in Kobe, Japan, linking central Kobe with the artificial island of Port Island.
  • E. Sullivan Line
    The Sullivan Line is a historic surveyed boundary line that played a key role in defining the border between the U.S. states of Missouri and Iowa.
  • 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_69e0c47fab1081908dc74a6545dbb051 completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f12459e1848190aa8d4ccc97f434b8 completed April 28, 2026, 9:19 p.m.
Created at: April 16, 2026, 8:01 p.m.