Triple

T14862539
Position Surface form Disambiguated ID Type / Status
Subject Lisarow railway station E349532 entity
Predicate locatedIn P40 FINISHED
Object Lisarow E1088234 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: Lisarow | Statement: [Lisarow railway station, locatedIn, Lisarow]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lisarow
Context triple: [Lisarow railway station, locatedIn, Lisarow]
  • A. Lisarow chosen
    Lisarow is a semi-rural suburb on the Central Coast of New South Wales, Australia, known for its residential areas, light industry, and proximity to major transport links.
  • B. Leyhof
    Leyhof is a residential neighborhood in the Dutch town of Leiderdorp, located in the province of South Holland.
  • C. Liluah
    Liluah is a suburban locality in the Howrah district of West Bengal, India, known for its residential areas and railway facilities near Kolkata.
  • D. Piershil
    Piershil is a small village in the Dutch province of South Holland, known for its rural character and location on the island of Hoeksche Waard.
  • E. Nouster
    Nouster is a small settlement on the Orkney island of North Ronaldsay in Scotland.
  • 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_69d822ed7e1881909b90fca143ad7e34 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69ded573cba881908d6d9ac570a64e5f completed April 15, 2026, 12:01 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe650c41b081909cdadbaec472eee3 completed May 8, 2026, 10:34 p.m.
Created at: April 10, 2026, 1:54 a.m.