Triple
T29944244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sémillon–Sauvignon Blanc–Muscadelle |
E760588
|
entity |
| Predicate | derivesFreshnessFrom |
P171288
|
FINISHED |
| Object | Sauvignon Blanc |
—
|
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: Sauvignon Blanc | Statement: [Sémillon–Sauvignon Blanc–Muscadelle, derivesFreshnessFrom, Sauvignon Blanc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derivesFreshnessFrom Context triple: [Sémillon–Sauvignon Blanc–Muscadelle, derivesFreshnessFrom, Sauvignon Blanc]
-
A.
isFreshnessIndicator
Indicates that something serves as a sign or measure of how fresh another item or product is.
-
B.
derivesRichnessFrom
chosen
Indicates that one entity obtains or enhances its richness, depth, or complexity as a result of another entity.
-
C.
effectiveUntilReplacedBy
Indicates that something remains valid or in force up to the point when it is superseded by a specified replacement.
-
D.
statusDerivedFrom
Indicates that one entity’s status is obtained, inferred, or inherited from the status of another entity.
-
E.
observedSince
Indicates that one entity has been continuously or repeatedly observed starting from a specified point in time.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 6:23 p.m.