Triple
T479151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pisco sour |
E9126
|
entity |
| Predicate | commonVariation |
P4680
|
FINISHED |
| Object | Chilean pisco sour |
—
|
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: Chilean pisco sour | Statement: [pisco sour, commonVariation, Chilean pisco sour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonVariation Context triple: [pisco sour, commonVariation, Chilean pisco sour]
-
A.
culturalVariation
Indicates that there are differences in practices, beliefs, or expressions between cultures or within a culture across groups, contexts, or time.
-
B.
variant
chosen
Indicates that one entity is an alternative form, version, or variation of another entity.
-
C.
typicalVariety
Indicates that one entity is a representative or characteristic example of the variety or type defined by another entity.
-
D.
commonIn
Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
-
E.
usageVariesBy
Indicates that the way something is used differs depending on a specified factor, such as context, user, location, or conditions.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f056459881909749764cc4a7f9e8 |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edf1d5848190a7da27e2fddc136f |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.