Triple

T7382755
Position Surface form Disambiguated ID Type / Status
Subject Lanark E170299 entity
Predicate hasPostTown P2711 FINISHED
Object LANARK E170299 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: LANARK | Statement: [Lanark, hasPostTown, LANARK]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: LANARK
Context triple: [Lanark, hasPostTown, LANARK]
  • A. Lanark chosen
    Lanark is a historic market town in South Lanarkshire, Scotland, known for its medieval origins and role as a former royal burgh.
  • B. Lanark
    Lanark is a small unincorporated community located in Raleigh County, West Virginia, United States.
  • C. Larbert
    Larbert is a small town in central Scotland, situated in the Falkirk council area and historically known for its industrial heritage and transport links.
  • D. Coatbridge
    Coatbridge is a town in North Lanarkshire, Scotland, historically known for its heavy industry and ironworks during the 19th century.
  • E. Vale of Leven
    Vale of Leven is a district in West Dunbartonshire, Scotland, known for its historic textile industry and location between Loch Lomond and the River Clyde.
  • 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_69c68a5d0ed08190b6d361e68f813330 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f1c9a3c48190972126c19aa31dca completed March 27, 2026, 9:08 p.m.
NED1 Entity disambiguation (via context triple) batch_69c802dee7448190be1835bd822b9180 completed March 28, 2026, 4:33 p.m.
Created at: March 27, 2026, 3:08 p.m.