Triple
T18046628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hondarrabi Zuri |
E431793
|
entity |
| Predicate | sparklingStyleAssociation |
P55208
|
FINISHED |
| Object | lightly sparkling Txakoli |
—
|
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: lightly sparkling Txakoli | Statement: [Hondarrabi Zuri, sparklingStyleAssociation, lightly sparkling Txakoli]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sparklingStyleAssociation Context triple: [Hondarrabi Zuri, sparklingStyleAssociation, lightly sparkling Txakoli]
-
A.
sparklingType
Indicates that one entity is classified as a specific type or category within the broader class of sparkling items or phenomena.
-
B.
wineStylesAssociatedWith
chosen
Indicates a relationship where certain wine styles are linked or connected to a particular entity, such as a region, grape, producer, or product.
-
C.
hasSparklingWine
Indicates that an entity possesses, includes, or is associated with sparkling wine.
-
D.
sparklingWineAllowed
Indicates that the use, serving, or presence of sparkling wine is permitted in the given context or under specified conditions.
-
E.
hasLuster
Indicates that one entity possesses a shiny, glossy, or reflective surface quality.
- 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4bff2d3c48190875ffe9c042d3ec0 |
completed | April 19, 2026, 11:43 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.