Triple
T31176298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fiano di Avellino wine |
E794758
|
entity |
| Predicate | DOCGStatus |
P171218
|
FINISHED |
| Object | granted in 2003 |
—
|
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: granted in 2003 | Statement: [Fiano di Avellino wine, DOCGStatus, granted in 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DOCGStatus Context triple: [Fiano di Avellino wine, DOCGStatus, granted in 2003]
-
A.
DOCStatus
Indicates the current state or condition of a document within a defined process or lifecycle.
-
B.
DOStatus
Indicates the current state or condition of an action, process, or obligation, such as whether it is pending, active, completed, or otherwise resolved.
-
C.
CDPStatus
Indicates the current operational or lifecycle state assigned to an entity within the CDP (Customer Data Platform) context.
-
D.
hasDocumentationStatus
Indicates the current state or condition of documentation associated with an entity, such as whether it exists, is complete, or is up to date.
-
E.
deFactoStatus
Indicates that one entity holds a role, position, or status in practice or by custom, even if it is not formally or legally recognized.
- 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_69f224d5b9708190b6ca79ad2fd3a28a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c6f01e881908fa84f5d429d37ae |
completed | May 3, 2026, 12:53 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f69c2127088190ae92c72461576d3b |
completed | May 3, 2026, 12:51 a.m. |
Created at: April 29, 2026, 9:08 p.m.