Triple

T26396365
Position Surface form Disambiguated ID Type / Status
Subject Armadale, West Lothian E663567 entity
Predicate hasSportsFacility P105 FINISHED
Object Armadale Stadium
Armadale Stadium is a sports venue in Armadale, West Lothian, best known as a motorcycle speedway track and former greyhound racing stadium.
E1744538 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: Armadale Stadium | Statement: [Armadale, West Lothian, hasSportsFacility, Armadale Stadium]
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: Armadale Stadium
Triple: [Armadale, West Lothian, hasSportsFacility, Armadale Stadium]
Generated description
Armadale Stadium is a sports venue in Armadale, West Lothian, best known as a motorcycle speedway track and former greyhound racing stadium.

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_69ee883823988190b418b111be28a44a completed April 26, 2026, 9:48 p.m.
NER Named-entity recognition batch_69f610c3adc481908a3df0856345498f completed May 2, 2026, 2:57 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12130b7db081909723421be86869cf completed May 23, 2026, 8:50 p.m.
NEDg Description generation batch_6a1215655aac8190b3f1a131550befc2 completed May 23, 2026, 9 p.m.
NED2 Entity disambiguation (via description) batch_6a1216420ef08190b33368157a089c98 completed May 23, 2026, 9:04 p.m.
Created at: April 26, 2026, 11:29 p.m.