Triple

T18181783
Position Surface form Disambiguated ID Type / Status
Subject Livingston, Scotland E435302 entity
Predicate hasNeighbourhood P4813 FINISHED
Object Almondvale 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: Almondvale | Statement: [Livingston, Scotland, hasNeighbourhood, Almondvale]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Almondvale
Context triple: [Livingston, Scotland, hasNeighbourhood, Almondvale]
  • A. Almondvale chosen
    Almondvale is a district of Livingston in West Lothian, Scotland, known for its major shopping centre and retail facilities.
  • B. Gardenvale
    Gardenvale is a suburban railway station in Melbourne, Australia, serving the local community on the Sandringham line.
  • C. Woodvale
    Woodvale is a rural locality within Queensland’s Banana Shire, known for its agricultural landscape and small-community character.
  • D. Meadvale
    Meadvale is a residential suburb and locality within the borough of Reigate and Banstead in Surrey, England.
  • E. Wellswood
    Wellswood is a leafy, affluent residential area of Torquay in Devon, England, known for its Victorian architecture, local shops, and proximity to coastal attractions.
  • 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_69d8b90c7ec081909b4694ccecb449c6 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4dffb3bc88190a627be9c444d5c7d completed April 19, 2026, 2 p.m.
Created at: April 10, 2026, 10:31 a.m.