Triple

T21390763
Position Surface form Disambiguated ID Type / Status
Subject Ballantrae E527640 entity
Predicate nearbySettlement P350 FINISHED
Object Lendalfoot 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: Lendalfoot | Statement: [Ballantrae, nearbySettlement, Lendalfoot]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lendalfoot
Context triple: [Ballantrae, nearbySettlement, Lendalfoot]
  • A. Lendalfoot chosen
    Lendalfoot is a small coastal village in southwest Scotland, situated along the Firth of Clyde in South Ayrshire.
  • B. Kershopefoot
    Kershopefoot is a small rural settlement in the Liddesdale area of the Scottish Borders, near the border with England.
  • C. Stonefoots
    Stonefoots is a prominent Dwarven house known within fantasy lore for its sturdy lineage and traditional craftsmanship.
  • D. Hillfoots
    Hillfoots is a region in central Scotland at the base of the Ochil Hills, encompassing several small towns and villages.
  • E. Harefoot
    Harefoot is the nickname of Harold Harefoot, an 11th-century King of England known for his swift, decisive rule during a turbulent succession period.
  • 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_69e0b51ff3748190935c0a513c62a12b completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e8b112a7808190ae4b180ce0d2b408 completed April 22, 2026, 11:29 a.m.
Created at: April 16, 2026, 5:13 p.m.