Triple

T7145836
Position Surface form Disambiguated ID Type / Status
Subject PA postcode area E166565 entity
Predicate covers P1393 FINISHED
Object Paisley E25349 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: Paisley | Statement: [PA postcode area, covers, Paisley]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Paisley
Context triple: [PA postcode area, covers, Paisley]
  • A. Paisley chosen
    Paisley is a large town in the west of Scotland known for its historic textile industry and as the origin of the famous paisley pattern.
  • B. Motherwell
    Motherwell is a former industrial town in North Lanarkshire, Scotland, historically known as a major center of the steel industry.
  • C. Uddingston
    Uddingston is a suburban town in Scotland, situated near Glasgow and known for its residential character and local amenities.
  • D. Shotts
    Shotts is a small town in central Scotland known historically for its coal mining and industrial heritage.
  • E. Rothesay
    Rothesay is a historic Scottish town on the Isle of Bute, known as a former royal burgh and traditional residence of Scottish monarchs.
  • 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_69c6888579d481909e05a8d6b81bf733 completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e7d3c48c8190a71a61a1d50cd7da completed March 27, 2026, 8:25 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7b8ee0244819084d5dfb3ee64149b completed March 28, 2026, 11:18 a.m.
Created at: March 27, 2026, 2:46 p.m.