Triple
T33068311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashdown Park |
E846162
|
entity |
| Predicate | isHeritageProperty |
P923
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ashdown Park, isHeritageProperty, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHeritageProperty Context triple: [Ashdown Park, isHeritageProperty, true]
-
A.
hasHeritageDesignation
Indicates that an entity has been formally assigned a specific heritage or cultural protection status by an authoritative body.
-
B.
isPartOfHeritage
Indicates that something belongs to, contributes to, or is recognized as a component of a broader cultural, historical, or natural heritage.
-
C.
hasHeritageListedPlace
Indicates that an entity possesses or is associated with a place that is officially designated as heritage-listed.
-
D.
cityHeritageStatus
Indicates that a city holds a specific heritage designation or status, such as being recognized for its historical, cultural, or architectural significance.
-
E.
heritageStatus
chosen
Indicates that an entity holds a particular cultural, historical, or natural heritage designation or protection status.
- 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_69f3495405b88190967af2157b43b896 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:25 a.m.