Triple
T16246073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cinsault |
E394373
|
entity |
| Predicate | hasYieldPotential |
P32569
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Cinsault, hasYieldPotential, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasYieldPotential Context triple: [Cinsault, hasYieldPotential, high]
-
A.
yieldPotential
chosen
Indicates the expected amount or capacity of output, production, or benefit that something can generate under given conditions.
-
B.
hasYield
Indicates that one entity produces, returns, or generates a measurable output, result, or profit for another entity or context.
-
C.
hasResourcePotential
Indicates that an entity possesses the capacity or suitability to provide, generate, or support a particular resource in the future.
-
D.
hasYard
Indicates that one entity possesses or includes a yard as part of its property or premises.
-
E.
hasPotential
Indicates that an entity possesses the capacity or possibility to develop, achieve, or exhibit a particular state, quality, or outcome in the future.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24561d250819096f709ea8751fcb9 |
completed | April 17, 2026, 2:36 p.m. |
| PD | Predicate disambiguation | batch_69e219ee6f6481909663b388dc99770a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.