Triple
T35302770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minahasa culture |
E1019545
|
entity |
| Predicate | culinaryCharacteristic |
P17157
|
FINISHED |
| Object | extensive use of chili |
—
|
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: extensive use of chili | Statement: [Minahasa culture, culinaryCharacteristic, extensive use of chili]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: culinaryCharacteristic Context triple: [Minahasa culture, culinaryCharacteristic, extensive use of chili]
-
A.
cuisineFeature
chosen
Indicates a characteristic, quality, or notable aspect that describes or distinguishes a particular cuisine.
-
B.
culinaryUse
Indicates that one entity is used in the preparation, flavoring, or serving of food or drink for another entity.
-
C.
fruitCharacteristic
Indicates that a specified characteristic or property is attributed to a particular fruit.
-
D.
seasoningStyle
Indicates the characteristic way in which an item is flavored or seasoned, such as the method, intensity, or cultural style of its seasoning.
-
E.
isSavory
Indicates that something has a salty, spicy, or umami-dominant taste rather than a sweet one.
- 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7904becb8819099bfe08009854ba5 |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.