Triple
T31736596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drummond Castle |
E810014
|
entity |
| Predicate | gardenStatus |
P172485
|
FINISHED |
| Object | Inventory of Gardens and Designed Landscapes in Scotland |
—
|
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: Inventory of Gardens and Designed Landscapes in Scotland | Statement: [Drummond Castle, gardenStatus, Inventory of Gardens and Designed Landscapes in Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gardenStatus Context triple: [Drummond Castle, gardenStatus, Inventory of Gardens and Designed Landscapes in Scotland]
-
A.
gardenValue
Indicates that one entity assigns or possesses a particular value, worth, or importance in relation to a garden.
-
B.
gardenAccess
Indicates that one entity is permitted to enter or use a particular garden area.
-
C.
containsGarden
Indicates that one entity includes or has a garden within its area or boundaries.
-
D.
gardenFeature
Indicates that one entity serves as a feature, element, or component within a garden associated with another entity.
-
E.
gardenManagedBy
Indicates that a garden is overseen, maintained, or administered by a particular person, group, or organization.
- F. None of above. chosen
Provenance (4 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_69f348e0e4908190a884582eca646fb7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abe15d5c81909ccf4ce37f78bc43 |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aaf31a548190b2f792ff4b8c002a |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 30, 2026, 11:23 p.m.