Triple
T31549998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tulip Festival in Morges |
E804971
|
entity |
| Predicate | drawsGardenEnthusiasts |
P172870
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tulip Festival in Morges, drawsGardenEnthusiasts, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drawsGardenEnthusiasts Context triple: [Tulip Festival in Morges, drawsGardenEnthusiasts, yes]
-
A.
roleInButchartGardens
Indicates that an entity holds or held a specific role, position, or function within the context of Butchart Gardens.
-
B.
gardensStyle
Indicates the stylistic design or aesthetic tradition according to which a garden is created or arranged.
-
C.
gardeningConcept
Indicates a conceptual or thematic relationship involving gardening, such as ideas, practices, or principles related to garden work or cultivation.
-
D.
gardenFeature
Indicates that one entity serves as a feature, element, or component within a garden associated with another entity.
-
E.
gardeningSpecialty
Indicates that an entity has a particular area of expertise or focus within the broader practice of gardening.
- 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_69f348d11a048190a65eb8384a3754ac |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 30, 2026, 10:10 p.m.