Triple
T29633757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Racine, Wisconsin |
E755653
|
entity |
| Predicate | hasHeritageFestival |
P2955
|
FINISHED |
| Object | Danish-related events |
—
|
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: Danish-related events | Statement: [Racine, Wisconsin, hasHeritageFestival, Danish-related events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeritageFestival Context triple: [Racine, Wisconsin, hasHeritageFestival, Danish-related events]
-
A.
hasFestival
Indicates that a location, community, or entity hosts or holds a festival or celebratory event.
-
B.
hasCulturalEvent
chosen
Indicates that a cultural event (such as a festival, performance, or exhibition) takes place in, is associated with, or is hosted by a given entity.
-
C.
hasFestivalSite
Indicates that a location or site is designated or used as the venue where a festival takes place.
-
D.
hasFestivalSection
Indicates that something includes or is associated with a specific section or category within a festival.
-
E.
hasFestivalDepicted
Indicates that a work or representation includes a depiction or portrayal of a festival.
- 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_69f0ef88fbe081908f0ad90c1c413f1c |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 28, 2026, 6:42 p.m.