Triple
T31334788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Espelette |
E799139
|
entity |
| Predicate | pepperForm |
P12789
|
FINISHED |
| Object | dried strings of peppers |
—
|
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: dried strings of peppers | Statement: [Espelette, pepperForm, dried strings of peppers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pepperForm Context triple: [Espelette, pepperForm, dried strings of peppers]
-
A.
potentialForm
Indicates that an action is expressed in its potential form, meaning the subject has the ability or possibility to perform that action.
-
B.
formsPreambleOf
Indicates that one element serves as the introductory or preface section to another, typically larger, document or text.
-
C.
preparationForm
Indicates the specific way a substance or product has been prepared or formulated for use (e.g., tablet, solution, cream).
-
D.
typicalForm
chosen
Indicates that one entity represents the standard, characteristic, or most common form or shape in which another entity typically appears or is realized.
-
E.
formsFor
Indicates that one entity constitutes the physical or structural makeup of 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_69f224e3f6ac8190a13488516abca7c9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 29, 2026, 9:16 p.m.