Triple

T26912229
Position Surface form Disambiguated ID Type / Status
Subject Airdrie and Shotts E677419 entity
Predicate createdFrom P5574 FINISHED
Object Monklands East
Monklands East was a former UK parliamentary constituency in Scotland that was later largely replaced by the Airdrie and Shotts constituency.
E214127 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: Monklands East | Statement: [Airdrie and Shotts, createdFrom, Monklands East]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Monklands East
Triple: [Airdrie and Shotts, createdFrom, Monklands East]
Generated description
Monklands East was a former UK parliamentary constituency in Scotland that was later largely replaced by the Airdrie and Shotts constituency.

Provenance (5 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_69eee9bcef1c8190be88586bb902bb9b completed April 27, 2026, 4:44 a.m.
NER Named-entity recognition batch_69f61fdb5c308190940acedab5748270 completed May 2, 2026, 4:01 p.m.
NED1 Entity disambiguation (via context triple) batch_6a121eb338ec8190b4fc02f7714ffee7 completed May 23, 2026, 9:40 p.m.
NEDg Description generation batch_6a121f90eec08190bd18be556349e464 completed May 23, 2026, 9:43 p.m.
NED2 Entity disambiguation (via description) batch_6a12205e89f4819098a8901d520e9c7d completed May 23, 2026, 9:47 p.m.
Created at: April 27, 2026, 6:02 a.m.