Triple
T19396945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smithville Fiddlers’ Jamboree and Crafts Festival |
E485214
|
entity |
| Predicate | heldAnnuallyIn |
P7073
|
FINISHED |
| Object | July |
—
|
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: July | Statement: [Smithville Fiddlers’ Jamboree and Crafts Festival, heldAnnuallyIn, July]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldAnnuallyIn Context triple: [Smithville Fiddlers’ Jamboree and Crafts Festival, heldAnnuallyIn, July]
-
A.
typicallyHeldIn
Indicates that an event, activity, or process most commonly or usually takes place within a particular location, venue, or context.
-
B.
oftenHeldOn
Indicates that an event or activity typically takes place on a particular date, day, or time.
-
C.
annualEvent
chosen
Indicates that an event occurs once every year on a recurring basis.
-
D.
oftenHeldAs
Indicates that one entity is frequently regarded, considered, or believed to be in a particular way with respect to another entity or property.
-
E.
areHeldIn
Indicates that events, activities, or objects take place or are located within a particular venue, container, or setting.
- 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62573f5788190a635b92121db2cf7 |
completed | April 20, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:36 p.m.