Triple
T32204844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grande Chartreuse monastery |
E822639
|
entity |
| Predicate | liqueurDistilledAt |
P103681
|
FINISHED |
| Object | Voiron |
—
|
NE NERFINISHED |
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: Voiron | Statement: [Grande Chartreuse monastery, liqueurDistilledAt, Voiron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liqueurDistilledAt Context triple: [Grande Chartreuse monastery, liqueurDistilledAt, Voiron]
-
A.
liqueurProducedBy
Indicates that a particular liqueur is produced or manufactured by a specific producer or organization.
-
B.
distilledIn
chosen
Indicates that a substance or product has been produced or purified through a distillation process carried out at a specified location or facility.
-
C.
firstSpiritDistilled
Indicates that an entity is the initial spirit or batch produced through a distillation process from another entity.
-
D.
liqueurDExpeditionAdded
Indicates that a liqueur d’expédition (dosage) has been added to a sparkling wine after disgorgement.
-
E.
distilleryType
Indicates the specific kind or category of distillery associated with an entity (e.g., craft, industrial, micro, or regional type).
- 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_69f349093174819086e633c190a51aa8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bb3e928c819095aafcac5970e923 |
completed | May 3, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:36 a.m.