Triple
T11271249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skagit Valley Tulip Festival |
E266816
|
entity |
| Predicate | transportationRecommendation |
P28199
|
FINISHED |
| Object | personal vehicle |
—
|
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: personal vehicle | Statement: [Skagit Valley Tulip Festival, transportationRecommendation, personal vehicle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportationRecommendation Context triple: [Skagit Valley Tulip Festival, transportationRecommendation, personal vehicle]
-
A.
transportAdvisory
chosen
Indicates that guidance, warnings, or recommendations are being issued regarding transportation conditions, operations, or usage.
-
B.
transportationFunction
Indicates that one entity serves to move or carry another entity from one place to another.
-
C.
transportationNearby
Indicates that there is a transportation facility or service located close to the referenced entity.
-
D.
transportationPlanned
Indicates that an arrangement has been made for someone or something to be transported from one place to another.
-
E.
transportFocus
Indicates that an entity is the primary object or subject of a transportation action or movement event.
- 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9506204819089dc0827483bd948 |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d7879bc56c8190b2e8d2193f29de05 |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:31 p.m.