Triple
T29944243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sémillon–Sauvignon Blanc–Muscadelle |
E760588
|
entity |
| Predicate | derivesRichnessFrom |
P171288
|
FINISHED |
| Object | Sémillon |
—
|
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: Sémillon | Statement: [Sémillon–Sauvignon Blanc–Muscadelle, derivesRichnessFrom, Sémillon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derivesRichnessFrom Context triple: [Sémillon–Sauvignon Blanc–Muscadelle, derivesRichnessFrom, Sémillon]
-
A.
richness
Indicates that an entity possesses a high degree of abundance, complexity, or density in some valued attribute or resource.
-
B.
hasRichnessClass
Indicates that an entity is assigned to a particular richness category or level within a defined classification system.
-
C.
richIn
Indicates that something contains a high amount or concentration of a particular substance, quality, or resource.
-
D.
hasRich
Indicates that an entity possesses or is characterized by a high level of wealth, abundance, or valuable resources.
-
E.
richerThan
Indicates that one entity possesses greater wealth or financial resources than another entity.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69dfbf6ac8190ba2e6fc0adfd8b73 |
completed | May 3, 2026, 12:59 a.m. |
Created at: April 29, 2026, 6:23 p.m.