Triple
T8850889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vernaccia di San Gimignano wine |
E210633
|
entity |
| Predicate | isFirstDOCOfItaly |
P59622
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Vernaccia di San Gimignano wine, isFirstDOCOfItaly, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFirstDOCOfItaly Context triple: [Vernaccia di San Gimignano wine, isFirstDOCOfItaly, true]
-
A.
firstForCountry
chosen
Indicates that the subject is the first instance or occurrence of its type to happen or exist within the specified country.
-
B.
issuedDocument
Indicates that one entity has formally created and provided an official document to another entity.
-
C.
DOCEstablished
Indicates that a document or organization was formally created, founded, or brought into official existence at a specific time or by a specific agent.
-
D.
firstOrdinary
Indicates that the subject is the first entity to hold or occupy an ordinary (non-special, standard) position, role, or status in a given sequence or context.
-
E.
wasFirst
Indicates that one entity occurred, appeared, or held a position before another in time or sequence.
- 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.