Triple
T17208566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Butchart family |
E417664
|
entity |
| Predicate | convertedQuarryTo |
P126412
|
FINISHED |
| Object | ornamental gardens |
—
|
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 gardens | Statement: [Butchart family, convertedQuarryTo, ornamental gardens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convertedQuarryTo Context triple: [Butchart family, convertedQuarryTo, ornamental gardens]
-
A.
quarriedFor
Indicates that a location or source is excavated or mined in order to obtain a particular material or resource.
-
B.
quarryRegion
Indicates that a specified region is the location where quarrying or extraction activities take place.
-
C.
hasQuarries
Indicates that one entity possesses, contains, or is associated with one or more quarries used for extracting stone or similar materials.
-
D.
historicallyQuarriedIn
Indicates that a material or resource was extracted from a particular location during a past historical period.
-
E.
convertedIn
Indicates that one entity has been transformed, changed, or translated into another form, state, or representation within a specified context.
- 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_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. |
| PDg | Predicate description generation | batch_69e3873f62108190966c4e741ebd548d |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:38 a.m.