Triple
T19390961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canosini |
E485064
|
entity |
| Predicate | associatedWithLocalProducts |
P62838
|
FINISHED |
| Object | wine |
—
|
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: wine | Statement: [Canosini, associatedWithLocalProducts, wine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithLocalProducts Context triple: [Canosini, associatedWithLocalProducts, wine]
-
A.
relatedToProduct
chosen
Indicates a general association or connection between an entity and a specific product, without specifying the exact nature of that relationship.
-
B.
associatedWithLocality
Indicates a relationship where something has a connection or relevance to a specific geographic place or locality.
-
C.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
D.
associatedWithCityBranding
Indicates a relationship where something is connected to, involved in, or contributes to the branding or promotional identity of a city.
-
E.
associatedWithPromotion
Indicates a relationship in which an entity is connected to, involved in, or affected by a specific promotion or promotional activity.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61b44b70c81908e2f0deeabe4360f |
completed | April 20, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:36 p.m.