Triple
T9415130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pinot |
E226998
|
entity |
| Predicate | typicalClusterShape |
P12090
|
FINISHED |
| Object | tightly packed grape clusters |
—
|
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: tightly packed grape clusters | Statement: [Pinot, typicalClusterShape, tightly packed grape clusters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalClusterShape Context triple: [Pinot, typicalClusterShape, tightly packed grape clusters]
-
A.
clusterDensity
chosen
Indicates the degree to which elements within a cluster are closely packed or concentrated relative to its size or volume.
-
B.
arealCluster
Indicates that entities belong to the same spatially contiguous or closely grouped geographic area.
-
C.
dominantCluster
Indicates that one cluster in a set is the most influential or representative group relative to the others, often based on size, centrality, or impact.
-
D.
typeOfCluster
Indicates that one entity is classified as a specific kind or category of cluster in relation to another entity.
-
E.
coreShape
Indicates that one entity serves as the primary or central shape or geometric form of 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_69ca84359e7c819091148ba4b670e436 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd68c7bd648190b17f082883c98239 |
completed | April 1, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69cca54c37f88190bddccf28e5fe5c84 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:48 p.m.