Triple
T30093997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flora Day festival |
E764812
|
entity |
| Predicate | danceRoute |
P168441
|
FINISHED |
| Object | through houses, shops and gardens in Helston |
—
|
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: through houses, shops and gardens in Helston | Statement: [Flora Day festival, danceRoute, through houses, shops and gardens in Helston]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: danceRoute Context triple: [Flora Day festival, danceRoute, through houses, shops and gardens in Helston]
-
A.
danceAction
Indicates an action where an entity performs or engages in dancing, typically involving rhythmic or expressive body movements.
-
B.
danceFeature
Indicates that one entity serves as a notable characteristic, element, or attribute of a dance or dancing-related activity.
-
C.
danceProp
Indicates that one entity is used or involved as a prop in another entity’s dance performance or dancing activity.
-
D.
danceDirection
Indicates the direction or orientation in which the dancing action is performed or moves.
-
E.
danceBackground
Indicates that one entity serves as the background or setting for another entity’s dancing activity.
- 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_69f22474e4288190b5f895fe3974aa92 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67d8e989081909d062bcf86c82ca2 |
completed | May 2, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 7:06 p.m.