Triple
T12744064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | blanc de blancs Champagne |
E304557
|
entity |
| Predicate | alsoProducedAs |
P106682
|
FINISHED |
| Object | non-vintage Champagne |
—
|
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: non-vintage Champagne | Statement: [blanc de blancs Champagne, alsoProducedAs, non-vintage Champagne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoProducedAs Context triple: [blanc de blancs Champagne, alsoProducedAs, non-vintage Champagne]
-
A.
producedAs
Indicates that one entity is created, generated, or brought into existence as a result or output of another entity or process.
-
B.
alsoProducedInPattern
Indicates that something was additionally produced within the same pattern, process, or production context as another item or event.
-
C.
laterProducedIn
Indicates that one production event or version occurred after another in time.
-
D.
associatedProduction
Indicates that there is a related or connected production (such as a work, performance, or manufacturing process) linked to the subject entity.
-
E.
coProduced
Indicates that two or more entities jointly produced or created a work, project, or product together.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96406e97c8190b79081039847115c |
completed | April 10, 2026, 8:56 p.m. |
| PDg | Predicate description generation | batch_69d96d87078c819083ea724238992204 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:26 p.m.