Triple
T415585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Champagne |
E9584
|
entity |
| Predicate | typicalDosageCategories |
P14599
|
FINISHED |
| Object | Brut Nature |
—
|
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: Brut Nature | Statement: [Champagne, typicalDosageCategories, Brut Nature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDosageCategories Context triple: [Champagne, typicalDosageCategories, Brut Nature]
-
A.
typeOfAdministration
Indicates the specific form or system of administration applied to or governing an entity.
-
B.
administeredIn
Indicates that an action, treatment, or process is carried out or applied within a specific location, context, or jurisdiction.
-
C.
typicalCapacity
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
-
D.
quantityType
Indicates that one entity is the type or category of quantity to which another entity (a specific measured or measurable amount) belongs.
-
E.
administeredWithin
Indicates that one entity is given, applied, or carried out inside the spatial or temporal bounds of another entity (such as a location, container, or time period).
- 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eebde1d881908fb212bfba9d7c67 |
completed | Feb. 28, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69a2edcff4688190809d83d112ff25a5 |
completed | Feb. 28, 2026, 1:29 p.m. |
| PDg | Predicate description generation | batch_69a2eeb8545c8190a2b8517e7ed5b92e |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:09 p.m.