Triple
T32681963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kremstal |
E835609
|
entity |
| Predicate | DACFor |
P174786
|
FINISHED |
| Object | Grüner Veltliner |
—
|
NE NERFINISHED |
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: Grüner Veltliner | Statement: [Kremstal, DACFor, Grüner Veltliner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DACFor Context triple: [Kremstal, DACFor, Grüner Veltliner]
-
A.
dacType
Indicates that one entity is classified as a specific type or category of DAC (Digital-to-Analog Converter) in relation to another entity.
-
B.
hasDAC
Indicates that an entity includes, uses, or is equipped with a Digital-to-Analog Converter (DAC) component.
-
C.
DACStatus
Indicates the current state or condition of a digital-to-analog converter (DAC) in relation to its operation or performance.
-
D.
FPU
Indicates that one entity functions as or contains a floating-point unit responsible for performing arithmetic operations on non-integer (floating-point) numbers for another entity or within a system.
-
E.
hasInternalDACResolution
Indicates that an entity is associated with a specific internal digital-to-analog converter (DAC) resolution setting or value.
- F. None of above. chosen
Provenance (4 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_69f3493211388190993801216afbc2a7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c7e92f38819084db3081ae5de9ec |
completed | May 3, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c77500a08190b2bdeca33bd2ac08 |
completed | May 3, 2026, 3:56 a.m. |
Created at: May 1, 2026, 1:09 a.m.