Triple
T30829575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glenarm Castle Walled Garden |
E785172
|
entity |
| Predicate | gardeningFocus |
P119037
|
FINISHED |
| Object | ornamental horticulture |
—
|
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: ornamental horticulture | Statement: [Glenarm Castle Walled Garden, gardeningFocus, ornamental horticulture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gardeningFocus Context triple: [Glenarm Castle Walled Garden, gardeningFocus, ornamental horticulture]
-
A.
gardeningConcept
Indicates a conceptual or thematic relationship involving gardening, such as ideas, practices, or principles related to garden work or cultivation.
-
B.
gardeningSpecialty
chosen
Indicates that an entity has a particular area of expertise or focus within the broader practice of gardening.
-
C.
gardenFeature
Indicates that one entity serves as a feature, element, or component within a garden associated with another entity.
-
D.
gardensStyle
Indicates the stylistic design or aesthetic tradition according to which a garden is created or arranged.
-
E.
horticultureProduct
Indicates a relationship where something is a product or output resulting from horticultural activities or cultivation.
- 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_69f224b6642481909e8d701de2cd1a53 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f690f8eed08190ae78208498b04506 |
completed | May 3, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:44 p.m.