Triple
T8850887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vernaccia di San Gimignano wine |
E210633
|
entity |
| Predicate | DOCStatusGranted |
P50587
|
FINISHED |
| Object | 1966 |
—
|
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: 1966 | Statement: [Vernaccia di San Gimignano wine, DOCStatusGranted, 1966]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DOCStatusGranted Context triple: [Vernaccia di San Gimignano wine, DOCStatusGranted, 1966]
-
A.
grantedStatus
Indicates that an entity has been officially approved or given a particular status, permission, or privilege.
-
B.
statusGrantedOn
chosen
Indicates the date or time at which a particular status was officially conferred or became effective for an entity.
-
C.
DOCStatus
Indicates the current state or condition of a document within a defined process or lifecycle.
-
D.
mintStatusGranted
Indicates that an entity has been officially authorized or approved to mint (create or issue) something, such as tokens, assets, or items.
-
E.
documentTypeApproved
Indicates that a specific type or category of document has been formally reviewed and granted approval for use or processing.
- 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_69ca838a424c8190b1ecac115c2927e7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60c2300c819097b1ca6ebe2f749a |
completed | April 1, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69cc5c25b874819084c9ba391703e066 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:49 p.m.