Triple
T27747752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scheurebe |
E702032
|
entity |
| Predicate | mainGrowingRegion |
P150179
|
FINISHED |
| Object | Rheinhessen |
—
|
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: Rheinhessen | Statement: [Scheurebe, mainGrowingRegion, Rheinhessen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainGrowingRegion Context triple: [Scheurebe, mainGrowingRegion, Rheinhessen]
-
A.
notableGrowingArea
Indicates that a location is recognized as an important or prominent area for cultivating or producing a particular crop or product.
-
B.
isGrowthAreaFor
Indicates that a particular domain, skill, or area represents an opportunity or target for development or improvement for an entity.
-
C.
primaryCropRegion
chosen
Indicates that a region is a main or predominant area where a particular crop is grown or produced.
-
D.
majorGrowingCountry
Indicates that a country is experiencing significant economic or developmental growth and is considered one of the leading emerging nations.
-
E.
region1
Indicates that one entity is the first or primary region associated with, containing, or encompassing 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6371b9fbc819097044eacdcd7c324 |
completed | May 2, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:17 p.m.