Triple
T34569394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gwäss |
E887581
|
entity |
| Predicate | parentageRole |
P75214
|
FINISHED |
| Object | progenitor of many European grape varieties |
—
|
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: progenitor of many European grape varieties | Statement: [Gwäss, parentageRole, progenitor of many European grape varieties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentageRole Context triple: [Gwäss, parentageRole, progenitor of many European grape varieties]
-
A.
parentRelationship
chosen
Indicates a familial relationship in which one entity is the parent of another entity.
-
B.
parentageIncludes
Indicates that a given parentage or lineage set contains or encompasses a particular parent or ancestral relationship.
-
C.
parentageVariant
Indicates a relationship where one entity is a variant or alternative form of another entity’s parentage or parental assignment.
-
D.
parentalRoleTo
Indicates a parental relationship in which one entity holds a parent role with respect to another entity.
-
E.
motherRole
Indicates that one entity holds the role or function of a mother in relation to 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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
Created at: May 1, 2026, 2:02 a.m.