Triple
T25857229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | chimarrão |
E651379
|
entity |
| Predicate | drinkingStyle |
P121843
|
FINISHED |
| Object | passed from person to person |
—
|
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: passed from person to person | Statement: [chimarrão, drinkingStyle, passed from person to person]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drinkingStyle Context triple: [chimarrão, drinkingStyle, passed from person to person]
-
A.
drinkingHabit
Indicates an entity’s typical pattern or frequency of consuming alcoholic or other beverages.
-
B.
drinkingContext
chosen
Indicates the situational or environmental circumstances under which a drinking event occurs (such as time, place, social setting, or purpose).
-
C.
drinkFamily
Indicates a familial or close relational connection between two entities centered around drinking-related activities or contexts.
-
D.
drinksWith
Indicates that two entities consume beverages together, typically at the same time and place in a social context.
-
E.
traditionalDrink
Indicates that one entity is a beverage customarily consumed within the culture, heritage, or longstanding practices associated with 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_69e7ab39035c8190be15c8aaee1bb858 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f60268b1388190b38c6d70cd028ecf |
completed | May 2, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 8:01 a.m.