Triple
T32856419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jurançon Sec |
E840386
|
entity |
| Predicate | differenceFromJurançonMoelleux |
P61682
|
FINISHED |
| Object | lower residual sugar |
—
|
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: lower residual sugar | Statement: [Jurançon Sec, differenceFromJurançonMoelleux, lower residual sugar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: differenceFromJurançonMoelleux Context triple: [Jurançon Sec, differenceFromJurançonMoelleux, lower residual sugar]
-
A.
distinguéDe
Indicates that one entity is distinguished from or set apart as different from another entity.
-
B.
differenceFromCheddar
Indicates a relationship where something is characterized or measured by how it differs from cheddar.
-
C.
differIn
chosen
Indicates that two entities are not the same in at least one specified aspect, attribute, or value.
-
D.
differenceFromFranceAncient
Indicates that something is distinct from or contrasts with ancient France in some specified respect.
-
E.
MourvèdreContribution
Indicates the role or impact that Mourvèdre grapes have on the characteristics or qualities of a wine or blend.
- 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_69f349412c78819084459850e11d29f7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:17 a.m.