Triple

T129369
Position Surface form Disambiguated ID Type / Status
Subject Fürth E2619 entity
Predicate hasTwinTown P919 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: [Fürth, hasTwinTown, Paisley]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Paisley
Context triple: [Fürth, hasTwinTown, 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. Glasgow
    Glasgow is Scotland’s largest city, historically a major industrial and shipbuilding center, known for its rich cultural scene, distinctive architecture, and role as a key urban hub in the United Kingdom.
  • D. Coatbridge
    Coatbridge is a town in North Lanarkshire, Scotland, historically known for its heavy industry and ironworks during the 19th century.
  • E. Cumbernauld
    Cumbernauld is a post-war new town in North Lanarkshire, Scotland, known for its modernist planning and distinctive, often-criticized town centre architecture.
  • 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_69a2520c0f3481908b0ed054a2fca8d0 completed Feb. 28, 2026, 2:25 a.m.
NER Named-entity recognition batch_69a2576518e0819096b35d8af7a4d1bd completed Feb. 28, 2026, 2:48 a.m.
NED1 Entity disambiguation (via context triple) batch_69a405ef40248190b81d461f3b6d4baa completed March 1, 2026, 9:25 a.m.
Created at: Feb. 28, 2026, 2:30 a.m.