Triple
T20162248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhône AOC system |
E491737
|
entity |
| Predicate | governsProductType |
P46087
|
FINISHED |
| Object | red 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: red wine | Statement: [Rhône AOC system, governsProductType, red wine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsProductType Context triple: [Rhône AOC system, governsProductType, red wine]
-
A.
appliesToProductType
Indicates that something (such as a rule, offer, or condition) is relevant or applicable specifically to a certain type or category of product.
-
B.
regulatesProduct
chosen
Indicates that one entity exercises control or governance over the production, distribution, or characteristics of a product belonging to or associated with another entity.
-
C.
governsTypeOfUnit
Indicates that one entity has authority or control over the type or category of unit to which another entity belongs.
-
D.
governsAssetType
Indicates that one entity has authority or control over the rules, usage, or management of a particular type or class of asset.
-
E.
licensedProductType
Indicates the type or category of product for which a license has been granted.
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e667e505888190a05e26a3c5a0ede1 |
completed | April 20, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:34 p.m.