Triple
T33730645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nutisal |
E864262
|
entity |
| Predicate | usesProcessingMethod |
P924
|
FINISHED |
| Object | dry roasting |
—
|
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: dry roasting | Statement: [Nutisal, usesProcessingMethod, dry roasting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesProcessingMethod Context triple: [Nutisal, usesProcessingMethod, dry roasting]
-
A.
usesComputationMethod
Indicates that an entity performs its processing or decision-making by applying a specified computational method or algorithm.
-
B.
isProcessedBy
Indicates that an entity undergoes some form of handling, transformation, or treatment performed by another entity or agent.
-
C.
usedProcess
chosen
Indicates that an entity employed or applied a particular process to achieve a result or perform an action.
-
D.
requiresProcessingBy
Indicates that one entity must undergo handling, treatment, or transformation performed by another entity before a condition is met or a process can continue.
-
E.
processingUse
Indicates that one entity uses or applies another entity as part of a processing or transformation activity.
- 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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 1, 2026, 1:44 a.m.