Triple

T20728530
Position Surface form Disambiguated ID Type / Status
Subject Cardenden mining area E509503 entity
Predicate hasSettlement P1068 FINISHED
Object Cardenden NE NERFINISHED

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: Cardenden | Statement: [Cardenden mining area, hasSettlement, Cardenden]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cardenden
Context triple: [Cardenden mining area, hasSettlement, Cardenden]
  • A. Cardenden chosen
    Cardenden is a village in Fife, Scotland, known primarily as a former mining community with a railway station on the local commuter network.
  • B. Dalkeith
    Dalkeith is a historic town in Midlothian, Scotland, known for its market-town heritage and proximity to Edinburgh.
  • C. Dennistoun
    Dennistoun is a residential district in the East End of Glasgow, Scotland, known for its Victorian tenements and close proximity to the city centre.
  • D. Kincardine
    Kincardine is a small Scottish town on the north shore of the Firth of Forth, known for its historic bridge and industrial heritage.
  • E. Kincardine
    Kincardine is a lakeside town in Ontario, Canada, known for its scenic Lake Huron shoreline, historic lighthouse, and strong Scottish heritage.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4c4cc648190b45fda6e2b20af56 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c1e9ed708190ad8e371646630fea completed April 21, 2026, 12:16 a.m.
Created at: April 16, 2026, 12:30 p.m.