Triple
T12347175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crémant de Loire |
E294384
|
entity |
| Predicate | pressureTypical |
P102766
|
FINISHED |
| Object | around 4–6 bar |
—
|
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: around 4–6 bar | Statement: [Crémant de Loire, pressureTypical, around 4–6 bar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pressureTypical Context triple: [Crémant de Loire, pressureTypical, around 4–6 bar]
-
A.
typicalPressure
chosen
Indicates the usual or characteristic level of pressure typically associated with an entity, situation, or condition.
-
B.
pressureType
Indicates the specific category or kind of pressure associated with an entity or interaction.
-
C.
pressureRange
Indicates the range of pressure values within which a condition, process, or relationship is defined or valid.
-
D.
pressureContext
Indicates a situational or environmental condition in which entities experience or exert pressure, stress, or constraint on one another or on a shared context.
-
E.
pressureCapability
Indicates the maximum pressure an entity can safely exert, withstand, or operate under within a given context.
- 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_69d6ab6ccbec8190b09e2d357aa80064 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f7ba17481908b03af7316b28d9b |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ecb5efc819086a3530282278bb1 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.