Triple

T29260696
Position Surface form Disambiguated ID Type / Status
Subject Restoration of Earlshall Castle, Fife E741836 entity
Predicate location P40 FINISHED
Object Earlshall Castle
Earlshall Castle is a 16th-century fortified tower house in Fife, Scotland, noted for its well-preserved architecture and historic gardens.
E1911426 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: Earlshall Castle | Statement: [Restoration of Earlshall Castle, Fife, location, Earlshall Castle]
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: Earlshall Castle
Triple: [Restoration of Earlshall Castle, Fife, location, Earlshall Castle]
Generated description
Earlshall Castle is a 16th-century fortified tower house in Fife, Scotland, noted for its well-preserved architecture and historic gardens.

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_69f0912065c08190bddd23e20e8ef18e completed April 28, 2026, 10:51 a.m.
NER Named-entity recognition batch_69f664b1145881908aed111df0493cab completed May 2, 2026, 8:55 p.m.
NED1 Entity disambiguation (via context triple) batch_6a277bf1b158819089ccf7b70366b27e completed June 9, 2026, 2:35 a.m.
NEDg Description generation batch_6a277fe105cc8190bd2b4b0811107107 completed June 9, 2026, 2:52 a.m.
NED2 Entity disambiguation (via description) batch_6a2780aa64b88190a2aa299bf7c7bca3 completed June 9, 2026, 2:55 a.m.
Created at: April 28, 2026, 12:41 p.m.