Triple
T2070819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint-Émilion classification |
E44811
|
entity |
| Predicate | coversProduct |
P16090
|
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: [Saint-Émilion classification, coversProduct, red wine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversProduct Context triple: [Saint-Émilion classification, coversProduct, red wine]
-
A.
alsoCovers
Indicates that something extends its scope or applicability to include an additional subject, area, or case beyond what was originally covered.
-
B.
scopeOfProducts
chosen
Indicates the range or extent of products that fall under a particular category, responsibility, or context.
-
C.
hasCoverType
Indicates that one entity possesses or is associated with a specific type or category of cover.
-
D.
supportsProduct
Indicates that one entity provides assistance, compatibility, or necessary resources for the operation, use, or maintenance of a specified product.
-
E.
coverUpBy
Indicates that one entity conceals, suppresses, or hides the actions, information, or wrongdoing 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_69a88916c2b48190a5ca2e9b12cad3ed |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9f677108190aea3c8db7850c892 |
completed | March 7, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69abb7b0edac8190a58eabee55f73deb |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:41 p.m.