Triple
T30111119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helston |
E765277
|
entity |
| Predicate | FloraDayFeature |
P168824
|
FINISHED |
| Object | Furry Dance |
—
|
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: Furry Dance | Statement: [Helston, FloraDayFeature, Furry Dance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FloraDayFeature Context triple: [Helston, FloraDayFeature, Furry Dance]
-
A.
hasFloralFeature
Indicates that an entity possesses a specific floral characteristic, structure, or attribute.
-
B.
flowerUse
Indicates how a flower is used or purposed in a particular context (e.g., decorative, medicinal, culinary, or symbolic use).
-
C.
ornamentalFeature
Indicates that one entity serves as a decorative or embellishing feature of another entity.
-
D.
gardenFeature
Indicates that one entity serves as a feature, element, or component within a garden associated with another entity.
-
E.
hasRegionalFlower
Indicates that a region is associated with a specific flower designated as its symbolic or representative flower.
- 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67dbfc82081909ae5d04676627a6c |
completed | May 2, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676f73c3481909f01fa69851b7298 |
completed | May 2, 2026, 10:13 p.m. |
Created at: April 29, 2026, 7:10 p.m.