Triple
T32255036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lanesville, Indiana |
E823991
|
entity |
| Predicate | heritageFestivalFeatures |
P96461
|
FINISHED |
| Object | parades |
—
|
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: parades | Statement: [Lanesville, Indiana, heritageFestivalFeatures, parades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageFestivalFeatures Context triple: [Lanesville, Indiana, heritageFestivalFeatures, parades]
-
A.
heritageFestivalOccursIn
Indicates that a heritage festival takes place or is held within a specific location or area.
-
B.
festivalFeature
chosen
Indicates that a festival includes or showcases a particular element, activity, or attraction as one of its features.
-
C.
hasHeritageFeature
Indicates that an entity possesses or includes a feature recognized as part of cultural, historical, or natural heritage.
-
D.
festivalFocus
Indicates that a festival is centered around, dedicated to, or thematically focused on a particular subject, activity, or feature.
-
E.
culturalHeritageIncludes
Indicates that a cultural heritage entity encompasses, contains, or incorporates another cultural element, tradition, artifact, or practice as part of its overall heritage.
- 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_69f3490db0748190bfef6e50c95d39d3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 1, 2026, 12:41 a.m.