Triple
T30214826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bois des Moutiers |
E768175
|
entity |
| Predicate | gardenDesignedBy |
P184
|
FINISHED |
| Object | Gertrude Jekyll |
—
|
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: Gertrude Jekyll | Statement: [Bois des Moutiers, gardenDesignedBy, Gertrude Jekyll]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gardenDesignedBy Context triple: [Bois des Moutiers, gardenDesignedBy, Gertrude Jekyll]
-
A.
landscapeDesignedBy
Indicates that a particular landscape or outdoor environment was planned, created, or shaped by a specific designer or design entity.
-
B.
gardenManagedBy
Indicates that a garden is overseen, maintained, or administered by a particular person, group, or organization.
-
C.
designedBy
chosen
Indicates that one entity is the creator, planner, or architect responsible for the form or structure of another entity.
-
D.
gardensBuiltFor
Indicates that one entity (such as a garden or landscaped area) was created or designed specifically for the benefit, use, or purpose of another entity.
-
E.
roleInButchartGardens
Indicates that an entity holds or held a specific role, position, or function within the context of Butchart Gardens.
- 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ff517908190ad290edafd6c6f5f |
completed | May 2, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:33 p.m.