Triple
T22207888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gilmer, Texas |
E548862
|
entity |
| Predicate | festivalMainProduct |
P96461
|
FINISHED |
| Object | sweet potatoes |
—
|
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: sweet potatoes | Statement: [Gilmer, Texas, festivalMainProduct, sweet potatoes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: festivalMainProduct Context triple: [Gilmer, Texas, festivalMainProduct, sweet potatoes]
-
A.
mainFestival
Indicates that an event is the primary or central festival associated with a particular context, place, or entity.
-
B.
mainFestivalHubFor
Indicates that one location serves as the primary central hub or focal point for a particular festival.
-
C.
festivalFeature
chosen
Indicates that a festival includes or showcases a particular element, activity, or attraction as one of its features.
-
D.
mainFestivalDay
Indicates that a particular day is the primary or most significant day within a festival’s overall schedule.
-
E.
festivalSystem
Indicates a relationship where an entity is part of, managed by, or associated with a festival-related organizational or operational system.
- 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_69e11e3f7e04819089806d81d5ac431e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12b2936a481909aa84c7983ed49ee |
completed | April 28, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e71b4dcc408190a30429fb08fcf39e |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:36 p.m.