Triple

T11193578
Position Surface form Disambiguated ID Type / Status
Subject Seacombe E264863 entity
Predicate adjacentTo P224 FINISHED
Object Liscard E347829 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: Liscard | Statement: [Seacombe, adjacentTo, Liscard]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Liscard
Context triple: [Seacombe, adjacentTo, Liscard]
  • A. Liscard chosen
    Liscard is a district and commercial centre within the town of Wallasey on the Wirral Peninsula in Merseyside, England.
  • B. Bordon
    Bordon is a town in East Hampshire, England, historically known for its large army camp and military training facilities.
  • C. Reydon
    Reydon is a village and civil parish in the English county of Suffolk, located near the coastal town of Southwold.
  • D. Orlestone
    Orlestone is a civil parish and rural community in the Ashford district of Kent, England, known for its woodland and countryside character.
  • E. Liberton
    Liberton is a suburban residential area in the south of Edinburgh, Scotland, known for its historic parish church and views towards the Pentland Hills.
  • 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_69d6aa9eb9248190b20211772621b4bc completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e8be025481909d311b587418dfb2 completed April 9, 2026, 5:58 p.m.
NED1 Entity disambiguation (via context triple) batch_69e483f8ecf4819086f0bab3ca9ddcb4 completed April 19, 2026, 7:27 a.m.
Created at: April 8, 2026, 9:29 p.m.