Triple
T12385484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mourvèdre |
E295850
|
entity |
| Predicate | plantingRequirement |
P32783
|
FINISHED |
| Object | needs warm sites to ripen fully |
—
|
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: needs warm sites to ripen fully | Statement: [Mourvèdre, plantingRequirement, needs warm sites to ripen fully]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plantingRequirement Context triple: [Mourvèdre, plantingRequirement, needs warm sites to ripen fully]
-
A.
cultivationRequirement
chosen
Indicates the specific conditions or resources that must be met or provided for something to be successfully cultivated.
-
B.
plantedIn
Indicates that one entity has been placed or sown into another entity as its growing or containing medium.
-
C.
soilPreference
Indicates the type or condition of soil that an entity prefers or is best suited to grow or exist in.
-
D.
plantingStyle
Indicates the method or arrangement used to plant entities in relation to each other or their environment.
-
E.
plantedAt
Indicates that one entity has been planted or placed into the ground or a specific location at or in association with another entity.
- 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_69d6ad9e653c8190b1473c860ee53dae |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d93fbd489c819098233a111442762e |
completed | April 10, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69d93ed256788190b704cad171a4824e |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:54 p.m.