Triple
T33451529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montecucco |
E856653
|
entity |
| Predicate | recognizedAsDOCG |
P310
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Montecucco, recognizedAsDOCG, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedAsDOCG Context triple: [Montecucco, recognizedAsDOCG, 2011]
-
A.
recognizedAsDOC
Indicates that one entity is formally acknowledged or identified as a document (DOC) representation of another entity.
-
B.
containsDOCG
Indicates that one entity includes or encompasses a DOCG (Denominazione di Origine Controllata e Garantita) designation or item within it.
-
C.
recognizedAs
chosen
Indicates that one entity is acknowledged or accepted as having the identity, role, status, or classification of another entity.
-
D.
recognizesDocument
Indicates that one entity acknowledges the validity or authenticity of a document associated with another entity.
-
E.
notableDOCG
Indicates that there is a notable or especially significant DOCG (Denominazione di Origine Controllata e Garantita) designation associated with the subject.
- 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_69f3497281a08190b4705de0b5f26ba7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: May 1, 2026, 1:37 a.m.