Triple
T12903050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coxhoe Hall |
E308656
|
entity |
| Predicate | hasArchitecturalUse |
P22013
|
FINISHED |
| Object | private residence |
—
|
LITERAL 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: private residence | Statement: [Coxhoe Hall, hasArchitecturalUse, private residence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArchitecturalUse Context triple: [Coxhoe Hall, hasArchitecturalUse, private residence]
-
A.
architecturalUse
chosen
Indicates how a structure, space, or element is intended to be used or function within an architectural context.
-
B.
hasArchitecturalFeature
Indicates that one entity possesses, includes, or is characterized by a specific architectural feature or element.
-
C.
hasArchitecturalSignificance
Indicates that something possesses notable architectural qualities, importance, or influence that make it worthy of special attention or recognition.
-
D.
architectureCanUse
Indicates that a particular architecture is capable of employing, incorporating, or being built with a specified component, technique, or resource.
-
E.
hasHeritageUse
Indicates that something is used, managed, or valued in a way that relates to cultural, historical, or natural heritage.
- 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971820e008190bf8bc7c392c8bcbb |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:40 p.m.