Triple
T17208564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Butchart family |
E417664
|
entity |
| Predicate | beganDevelopingButchartGardens |
P10779
|
FINISHED |
| Object | early 20th century |
—
|
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: early 20th century | Statement: [Butchart family, beganDevelopingButchartGardens, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganDevelopingButchartGardens Context triple: [Butchart family, beganDevelopingButchartGardens, early 20th century]
-
A.
createdAsGarden
Indicates that something was brought into existence or established specifically in the form or function of a garden.
-
B.
developmentBegan
chosen
Indicates that the process of creating or developing something was initiated at a particular time or under certain conditions.
-
C.
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.
-
D.
hasBotanicalGarden
Indicates that one entity possesses, contains, or includes a botanical garden as part of its facilities or domain.
-
E.
usedAsImperialGardenUntil
Indicates that something served the function of an imperial garden up to a specified point in time.
- 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42dc3b0ec8190b8c9fc401da5770c |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.