Triple
T25815117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chianti Montalbano |
E650226
|
entity |
| Predicate | governingDOCG |
P18398
|
FINISHED |
| Object | Chianti DOCG |
—
|
NE NERFINISHED |
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: Chianti DOCG | Statement: [Chianti Montalbano, governingDOCG, Chianti DOCG]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingDOCG Context triple: [Chianti Montalbano, governingDOCG, Chianti DOCG]
-
A.
governingDocumentMentioned
Indicates that a governing document is referenced or cited in relation to the entities involved.
-
B.
governanceDocumentType
Indicates the specific category or type of formal governance document that defines rules, policies, or oversight for an entity or process.
-
C.
regulatoryDocument
chosen
Indicates a relationship where one entity serves as a regulatory document that defines rules, standards, or requirements governing another entity.
-
D.
governsBodyOfLaw
Indicates that one entity has authoritative control over the creation, interpretation, or enforcement of a particular body of law.
-
E.
governanceDocumentAuthored
Indicates that a specific governance document was written or created by a particular author or authors.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: April 22, 2026, 7:25 a.m.