Triple
T24378543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carrot Festival Parade |
E614544
|
entity |
| Predicate | mainAttractionOf |
P5644
|
FINISHED |
| Object | Holtville Carrot Festival |
—
|
NE NERFINISHED |
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: Holtville Carrot Festival | Statement: [Carrot Festival Parade, mainAttractionOf, Holtville Carrot Festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainAttractionOf Context triple: [Carrot Festival Parade, mainAttractionOf, Holtville Carrot Festival]
-
A.
isMajorAttractionFor
chosen
Indicates that something serves as a primary or highly significant draw or point of interest for a particular audience, group, or location.
-
B.
isMajorAttractionIn
Indicates that something is a primary or highly significant attraction within a particular place or location.
-
C.
alsoAttractsTouristsIn
Indicates that a place, in addition to another, draws or appeals to tourists within a specified location or context.
-
D.
relatedAttraction
Indicates that one attraction is associated with or connected to another attraction in some relevant way.
-
E.
attractionType
Indicates the specific kind or category of attraction that characterizes the relationship between entities.
- 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_69e2d7e362e481909e32fe4ef8269d4f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293d96e7c8190b2f33a8fd12c32c6 |
completed | April 29, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:02 a.m.