Triple

T7172073
Position Surface form Disambiguated ID Type / Status
Subject Malahide E167223 entity
Predicate nearbySettlement P350 FINISHED
Object Kinsealy E152079 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: Kinsealy | Statement: [Malahide, nearbySettlement, Kinsealy]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kinsealy
Context triple: [Malahide, nearbySettlement, Kinsealy]
  • A. Kinsealy chosen
    Kinsealy is a suburban locality in north County Dublin, Ireland, known for its residential character and proximity to Swords and Dublin city.
  • B. Kelshall
    Kelshall is a small rural village in the North Hertfordshire district of England, characterized by its historic church and agricultural surroundings.
  • C. Kincorth
    Kincorth is a residential area in the south of Aberdeen, Scotland, known for its post-war housing and proximity to the River Dee.
  • D. Southesk
    Southesk is the traditional war cry associated with Clan Carnegie, a Scottish noble family from Angus.
  • E. Leagrave
    Leagrave is a suburban area of Luton in Bedfordshire, England, known as the district where the River Lea originates.
  • 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_69c68889a2748190a316c5e65360361a completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e88b0a448190a19bd2d9e2a310a4 completed March 27, 2026, 8:28 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7b918a838819088bd24d462101902 completed March 28, 2026, 11:18 a.m.
Created at: March 27, 2026, 2:48 p.m.