Triple
T25876376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Modica chocolate |
E651912
|
entity |
| Predicate | typicalCocoaContent |
P195716
|
FINISHED |
| Object | high cocoa percentage |
—
|
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: high cocoa percentage | Statement: [Modica chocolate, typicalCocoaContent, high cocoa percentage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCocoaContent Context triple: [Modica chocolate, typicalCocoaContent, high cocoa percentage]
-
A.
typicalContentDescriptors
Indicates the usual or characteristic types of content or attributes that are commonly associated with an entity.
-
B.
typicalApplicationWindow
Indicates that something is a standard or commonly used application window in a software environment.
-
C.
typicalInterface
Indicates that one entity serves as the standard or commonly used interface through which another entity is accessed or interacted with.
-
D.
caskTypesUsed
Indicates that certain types of casks are used in relation to a given entity or process.
-
E.
typicalContentStyle
Indicates the usual or characteristic manner, format, or stylistic approach in which content associated with an entity is presented.
- F. None of above. chosen
Provenance (4 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_69e7ab3ad9d88190841ddcb93ab02e96 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
| PDg | Predicate description generation | batch_69fde49953c481909ac352ab36fa9ff2 |
completed | May 8, 2026, 1:26 p.m. |
Created at: April 22, 2026, 8:12 a.m.