Triple
T17208567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Butchart family |
E417664
|
entity |
| Predicate | associatedWithAttractionType |
P8648
|
FINISHED |
| Object | botanical garden |
—
|
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: botanical garden | Statement: [Butchart family, associatedWithAttractionType, botanical garden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithAttractionType Context triple: [Butchart family, associatedWithAttractionType, botanical garden]
-
A.
hasAttractionType
chosen
Indicates that one entity is associated with a specific kind or category of attraction (e.g., tourist, cultural, natural).
-
B.
partOfAttractionType
Indicates that one attraction type is a component or subset of a broader, more general attraction type.
-
C.
hasPrimaryAttractionType
Indicates that an entity is characterized by a main or dominant type of attraction or appeal it offers.
-
D.
attractionType
Indicates the specific kind or category of attraction that characterizes the relationship between entities.
-
E.
relatedAttraction
Indicates that one attraction is associated with or connected to another attraction in some relevant way.
- 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.