Triple
T14915442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ephraim, Wisconsin |
E371369
|
entity |
| Predicate | FyrBalFestivalTradition |
P44899
|
FINISHED |
| Object | bonfires along the shoreline |
—
|
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: bonfires along the shoreline | Statement: [Ephraim, Wisconsin, FyrBalFestivalTradition, bonfires along the shoreline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FyrBalFestivalTradition Context triple: [Ephraim, Wisconsin, FyrBalFestivalTradition, bonfires along the shoreline]
-
A.
folkFestivalFormerName
Indicates that a folk festival previously had a different official name than the one it currently holds.
-
B.
festivalSystem
Indicates a relationship where an entity is part of, managed by, or associated with a festival-related organizational or operational system.
-
C.
festivalAlsoKnownAs
Indicates that a festival is referred to by an alternative name or alias.
-
D.
festivalFounded
Indicates that a particular festival was established or created by a specific person, group, or organization.
-
E.
festivalFocus
chosen
Indicates that a festival is centered around, dedicated to, or thematically focused on a particular subject, activity, or feature.
- 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded61f1d488190995f847f84d72cdc |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:28 a.m.