Triple
T15912719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sauternes |
E385886
|
entity |
| Predicate | allowsProductionOf |
P33286
|
FINISHED |
| Object | Sauternes AOC 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: Sauternes AOC wine | Statement: [Sauternes, allowsProductionOf, Sauternes AOC wine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsProductionOf Context triple: [Sauternes, allowsProductionOf, Sauternes AOC wine]
-
A.
eligibleProductionType
chosen
Indicates that a given entity qualifies for or is allowed to participate in a specified type or category of production.
-
B.
fromProduction
Indicates that something originates from, is derived from, or is produced by a particular production process, source, or facility.
-
C.
hasProduction
Indicates that an entity is associated with, or responsible for, the creation or manufacture of another entity or product.
-
D.
increasesProductionOf
Indicates that one entity causes a rise or enhancement in the amount or rate at which another entity is produced.
-
E.
hasProductionUse
Indicates that something is utilized or applied within a production or operational environment.
- 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_69d86da686e4819097cbf3b1fc2d881d |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e172b48b308190bc430b2308cbc75b |
completed | April 16, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69e142cf5c548190a931f7b58144cd31 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:52 a.m.