Triple
T26031298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Closeburn, Dumfriesshire |
E647436
|
entity |
| Predicate | hasMedievalTowerHouse |
P139972
|
FINISHED |
| Object | Closeburn Castle |
—
|
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: Closeburn Castle | Statement: [Closeburn, Dumfriesshire, hasMedievalTowerHouse, Closeburn Castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMedievalTowerHouse Context triple: [Closeburn, Dumfriesshire, hasMedievalTowerHouse, Closeburn Castle]
-
A.
hasMedievalBuilding
chosen
Indicates that one entity possesses, contains, or includes a building dating from the medieval period.
-
B.
hasMedievalElements
Indicates that something incorporates characteristics, motifs, or features typical of the medieval period.
-
C.
hasFamousCastle
Indicates that an entity possesses or is the location of a castle that is widely recognized or renowned.
-
D.
hasCastleTownHistory
Indicates that an entity has a historical association with a castle town, such as originating from, being located in, or significantly shaped by one.
-
E.
hasCastleRemains
Indicates that one entity possesses or contains the remaining structures or ruins of a castle associated with it.
- F. None of above.
Provenance (3 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 22, 2026, 9:06 a.m.