Triple
T21796344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canyon of Heroes |
E538103
|
entity |
| Predicate | paradeTradition |
P64101
|
FINISHED |
| Object | ticker tape thrown from office buildings |
—
|
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: ticker tape thrown from office buildings | Statement: [Canyon of Heroes, paradeTradition, ticker tape thrown from office buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paradeTradition Context triple: [Canyon of Heroes, paradeTradition, ticker tape thrown from office buildings]
-
A.
paradeIn
Indicates that an entity participates in or moves as part of a parade occurring at a specified place or time.
-
B.
paradeTime
Indicates the scheduled or actual time at which a parade takes place.
-
C.
mainParade
Indicates the relationship where an event or entity serves as the primary or central parade associated with a given context or occasion.
-
D.
establishedTradition
chosen
Indicates that something has become a customary, long-standing practice or convention that is regularly followed within a group, culture, or context.
-
E.
paradeDate
Indicates the calendar date on which a parade is scheduled to occur or took place.
- 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_69e0c4733f4081909a86622e7e6d15d2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0622502188190998638317f232334 |
completed | April 28, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:53 p.m.