Triple

T13283349
Position Surface form Disambiguated ID Type / Status
Subject St Marychurch E316376 entity
Predicate locatedInPartOfTown P40 FINISHED
Object northern Torquay LITERAL 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: northern Torquay | Statement: [St Marychurch, locatedInPartOfTown, northern Torquay]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedInPartOfTown
Context triple: [St Marychurch, locatedInPartOfTown, northern Torquay]
  • A. locatedInPlannedTown
    Indicates that an entity is situated within the boundaries of a town that has been deliberately planned or designed rather than having developed organically.
  • B. locatedIn chosen
    Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
  • C. usedInTown
    Indicates that something is utilized, applied, or functions within the context or boundaries of a particular town.
  • D. locatedInResortTown
    Indicates that something is situated within the boundaries of a town that is primarily known as a resort or vacation destination.
  • E. partlyInAdministrativeArea
    Indicates that an entity is located such that only a portion of it lies within a specified administrative area (e.g., a city, county, or region).
  • F. None of above.

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_69d806b349908190a9a61dd9323bf153 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d99cfdc9388190af1fdd3cd4717bd8 completed April 11, 2026, 12:59 a.m.
PD Predicate disambiguation batch_69d98f6535688190a5a4549b7be2d611 completed April 11, 2026, 12:01 a.m.
Created at: April 9, 2026, 9:27 p.m.