Triple
T16174153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grenache-Syrah-Mourvèdre |
E392518
|
entity |
| Predicate | hasComponentGrape |
P11949
|
FINISHED |
| Object | Grenache |
—
|
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: Grenache | Statement: [Grenache-Syrah-Mourvèdre, hasComponentGrape, Grenache]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComponentGrape Context triple: [Grenache-Syrah-Mourvèdre, hasComponentGrape, Grenache]
-
A.
supportsGrapeType
Indicates that one entity provides suitable conditions or compatibility for cultivating or using a particular grape type.
-
B.
usesGrapeType
chosen
Indicates that one entity employs or incorporates a specific type or variety of grape in its composition, production, or process.
-
C.
hasComponentGroup
Indicates that an entity includes or is associated with a specific group of components treated as a single unit.
-
D.
hasComponentModel
Indicates that an entity includes or is associated with a specific component model as part of its structure or configuration.
-
E.
hasComponentProgram
Indicates that one program includes or is composed of another program as a component or sub-program.
- 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21eb9b8208190b60874cec7a3a98e |
completed | April 17, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.