Triple
T6588439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sagarejo |
E159286
|
entity |
| Predicate | partOfWineIndustry |
P53749
|
FINISHED |
| Object | Georgian wine industry |
—
|
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: Georgian wine industry | Statement: [Sagarejo, partOfWineIndustry, Georgian wine industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfWineIndustry Context triple: [Sagarejo, partOfWineIndustry, Georgian wine industry]
-
A.
wineEconomyRole
chosen
Indicates the role or function an entity has within the wine-related economy, such as production, distribution, trade, or regulation.
-
B.
producesWine
Indicates that one entity creates or manufactures wine as a product.
-
C.
viticulturalRole
Indicates the specific function, responsibility, or involvement an entity has within viticulture or grape-growing activities.
-
D.
hasWinemaker
Indicates that one entity serves as the winemaker responsible for producing or overseeing the production of wine for another entity.
-
E.
hasWinemakingFacility
Indicates that an entity possesses or is associated with a facility where winemaking activities are carried out.
- 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_69c688366ce8819083f8883983c0df92 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6c07cdf048190945ca5810fb1de88 |
completed | March 27, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c6acfb462481909cb7aff5af4bca9d |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:55 p.m.