Triple
T16246094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cinsault |
E394373
|
entity |
| Predicate | hasRipeningTime |
P2080
|
FINISHED |
| Object | mid to late ripening |
—
|
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: mid to late ripening | Statement: [Cinsault, hasRipeningTime, mid to late ripening]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRipeningTime Context triple: [Cinsault, hasRipeningTime, mid to late ripening]
-
A.
ripeningTime
chosen
Indicates the period or duration required for something to become fully ripe or reach its mature, ready-to-use state.
-
B.
ripeningTimeRelative
Indicates the temporal relationship between this entity’s ripening period and a reference ripening period (e.g., earlier, later, or at the same time).
-
C.
mustBeMaturedIn
Indicates that something is required to undergo a maturation process within a specified context, condition, or environment before it is considered ready or valid.
-
D.
maturesIn
Indicates that an entity reaches full development, ripeness, or maturity within a specified time period or under certain conditions.
-
E.
hasMaturity
Indicates that an entity possesses a specified level, state, or stage of development or maturity.
- 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.