Triple
T12848263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manggahan Festival |
E307239
|
entity |
| Predicate | productCelebrated |
P83292
|
FINISHED |
| Object | Guimaras mangoes |
—
|
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: Guimaras mangoes | Statement: [Manggahan Festival, productCelebrated, Guimaras mangoes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productCelebrated Context triple: [Manggahan Festival, productCelebrated, Guimaras mangoes]
-
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.
byProduct
Indicates that one entity is produced incidentally or as a secondary result of a process, activity, or creation involving another entity.
-
C.
productTypePromoted
Indicates that a particular type or category of product is being actively promoted or highlighted, such as through marketing, placement, or special offers.
-
D.
productDomain
Indicates the domain, field, or area of application to which a given product belongs or is relevant.
-
E.
isCelebratoryOf
chosen
Indicates that something expresses celebration, honor, or festive recognition directed toward a particular event, person, or occasion.
- 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_69d7bdf5e7cc8190be357278bc5ba3bb |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714208f881908f7f8a921362909a |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa3002881908000357b1f95a3ac |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:36 p.m.