Triple
T34534407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Usher Gardens |
E886626
|
entity |
| Predicate | gardenPhilosophy |
P164388
|
FINISHED |
| Object | naturalistic planting |
—
|
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: naturalistic planting | Statement: [Mount Usher Gardens, gardenPhilosophy, naturalistic planting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gardenPhilosophy Context triple: [Mount Usher Gardens, gardenPhilosophy, naturalistic planting]
-
A.
gardeningConcept
chosen
Indicates a conceptual or thematic relationship involving gardening, such as ideas, practices, or principles related to garden work or cultivation.
-
B.
gardensStyle
Indicates the stylistic design or aesthetic tradition according to which a garden is created or arranged.
-
C.
gardenValue
Indicates that one entity assigns or possesses a particular value, worth, or importance in relation to a garden.
-
D.
gardenFeature
Indicates that one entity serves as a feature, element, or component within a garden associated with another entity.
-
E.
drawsGardenEnthusiasts
Indicates that something attracts or appeals to people who are enthusiastic about gardens or gardening.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71feb9138819081afa69a2e2aebf3 |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:02 a.m.