Triple
T36418919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parker County Peach Festival |
E897094
|
entity |
| Predicate | productFeatured |
P142626
|
FINISHED |
| Object | local peaches |
—
|
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: local peaches | Statement: [Parker County Peach Festival, productFeatured, local peaches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productFeatured Context triple: [Parker County Peach Festival, productFeatured, local peaches]
-
A.
productFor
Indicates that one entity is intended to be used by, with, or in relation to another entity as its product or offering.
-
B.
productWith
chosen
Indicates a relationship where one entity is associated with, contains, or is offered together with another entity as a product.
-
C.
productForm
Indicates the specific physical or presentation format in which a product is offered or delivered (e.g., tablet, liquid, package type).
-
D.
productExample
Indicates that one entity serves as an illustrative or sample instance of a product associated with another entity.
-
E.
providedProduct
Indicates that one entity has supplied or made available a particular product to another entity.
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff17be6ad48190963206f2619b1b28 |
completed | May 9, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69ff1724ba24819092c928fcbcb286ec |
completed | May 9, 2026, 11:14 a.m. |
Created at: May 3, 2026, 4:10 p.m.