Triple
T32003069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokaji Aszú |
E817184
|
entity |
| Predicate | formerPuttonyosRange |
P199815
|
FINISHED |
| Object | 3–6 puttonyos |
—
|
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: 3–6 puttonyos | Statement: [Tokaji Aszú, formerPuttonyosRange, 3–6 puttonyos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerPuttonyosRange Context triple: [Tokaji Aszú, formerPuttonyosRange, 3–6 puttonyos]
-
A.
formerCustom
Indicates that one entity was previously a customer of another entity but is no longer in that role.
-
B.
formerZone
Indicates that an entity was previously designated as a particular zone or area but no longer holds that status.
-
C.
formerPart
Indicates that an entity was once a component or member of another entity but is no longer part of it.
-
D.
eraBefore
Indicates that one time period or era chronologically precedes another.
-
E.
previousPeg
Indicates that one peg directly precedes another peg in a defined sequence or ordering.
- 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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff59b33a38819086cc9aa19b81748b |
completed | May 9, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69ff587758f88190a39c2164341dc554 |
completed | May 9, 2026, 3:53 p.m. |
| PDg | Predicate description generation | batch_69ff59b1e2ac8190bb65529e9dbbb178 |
completed | May 9, 2026, 3:58 p.m. |
Created at: May 1, 2026, 12:14 a.m.