Triple
T32255015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lanesville, Indiana |
E823991
|
entity |
| Predicate | heritageFestivalOccursIn |
P187066
|
FINISHED |
| Object | September |
—
|
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: September | Statement: [Lanesville, Indiana, heritageFestivalOccursIn, September]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageFestivalOccursIn Context triple: [Lanesville, Indiana, heritageFestivalOccursIn, September]
-
A.
festivalHeldIn
Indicates that a festival takes place or is hosted at a specific location or venue.
-
B.
festivalFoundedIn
Indicates that a festival was established or created in a specific year or time period.
-
C.
heritageLocation
Indicates that a location is recognized or designated as having cultural, historical, or natural heritage significance in relation to something.
-
D.
festivalFounded
Indicates that a particular festival was established or created by a specific person, group, or organization.
-
E.
locatedInFestival
Indicates that something exists or takes place within the spatial or organizational boundaries of a specific festival.
- F. None of above. chosen
Provenance (4 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_69f3490db0748190bfef6e50c95d39d3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb3424724c8190ba55ecf66fa0b171 |
completed | May 6, 2026, 12:29 p.m. |
Created at: May 1, 2026, 12:41 a.m.