Triple
T34026384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Cherry Blossom Festival Parade |
E872515
|
entity |
| Predicate | hasTicketedGrandstands |
P174346
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [National Cherry Blossom Festival Parade, hasTicketedGrandstands, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTicketedGrandstands Context triple: [National Cherry Blossom Festival Parade, hasTicketedGrandstands, true]
-
A.
hasGrandstandFeature
Indicates that something possesses or includes a grandstand-related feature or characteristic.
-
B.
hasGrandstandStyle
Indicates that something is characterized by or associated with a particular style or type of grandstand.
-
C.
hasTicketing
Indicates that an entity provides or is associated with a system or mechanism for issuing, managing, or selling tickets.
-
D.
hasTicketedArea
chosen
Indicates that an area is restricted to individuals who possess a valid ticket or fare authorization.
-
E.
hasTicketHall
Indicates that a place or facility includes or is equipped with a designated ticket hall area for purchasing or validating tickets.
- 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_69f349a2527c81909a7cd4bda94d70ad |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
Created at: May 1, 2026, 1:51 a.m.