Triple
T414159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tulip Time Festival |
E9554
|
entity |
| Predicate | mainAttraction |
P5644
|
FINISHED |
| Object | tulip displays |
—
|
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: tulip displays | Statement: [Tulip Time Festival, mainAttraction, tulip displays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainAttraction Context triple: [Tulip Time Festival, mainAttraction, tulip displays]
-
A.
isMajorAttractionFor
chosen
Indicates that something serves as a primary or highly significant draw or point of interest for a particular audience, group, or location.
-
B.
attractionType
Indicates the specific kind or category of attraction that characterizes the relationship between entities.
-
C.
isMajorAttractionIn
Indicates that something is a primary or highly significant attraction within a particular place or location.
-
D.
servesAttraction
Indicates that one entity functions as or provides a service that supports or enhances the experience of a particular attraction.
-
E.
containsAttraction
Indicates that one entity includes or encompasses an attraction (such as a point of interest, feature, or draw) within its bounds or scope.
- 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eebde1d881908fb212bfba9d7c67 |
completed | Feb. 28, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69a2edcff4688190809d83d112ff25a5 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:09 p.m.