Triple
T14019009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Champagne Jam |
E337276
|
entity |
| Predicate | hasPolishedProduction |
P112501
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Champagne Jam, hasPolishedProduction, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPolishedProduction Context triple: [Champagne Jam, hasPolishedProduction, true]
-
A.
hasProduction
Indicates that an entity is associated with, or responsible for, the creation or manufacture of another entity or product.
-
B.
hasProductionValue
Indicates that something possesses or is associated with a particular level or type of production quality or cost.
-
C.
hasProductionStatus
Indicates the current stage or condition of an entity’s production process (e.g., planned, in progress, completed, or discontinued).
-
D.
hasProductionMethod
Indicates that one entity is produced, created, or manufactured using the method, process, or technique specified by another entity.
-
E.
hasProductionAspect
Indicates that something possesses or involves a particular aspect, feature, or characteristic related to its production process or creation.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f3b5b088190a58715779d2c46a6 |
completed | April 14, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239524688190a0f2408c239cfcaa |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:19 p.m.