Triple
T30439548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apulian wines |
E774402
|
entity |
| Predicate | importantDOC |
P174310
|
FINISHED |
| Object | Primitivo di Manduria DOC |
—
|
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: Primitivo di Manduria DOC | Statement: [Apulian wines, importantDOC, Primitivo di Manduria DOC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importantDOC Context triple: [Apulian wines, importantDOC, Primitivo di Manduria DOC]
-
A.
importantOffice
Indicates that an entity holds or is associated with a position or office considered significant or high in importance within a given context.
-
B.
importantObject
Indicates that one entity is considered especially significant, central, or of high priority in relation to another entity or context.
-
C.
importantNote
Indicates that one entity is marked as an important or noteworthy note in relation to another entity.
-
D.
isImportantFor
Indicates that something holds significant value, relevance, or necessity in relation to something else.
-
E.
importantAria
Indicates that an aria is considered significant or central in its musical, dramatic, or contextual role.
- 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_69f22492d2a88190995ce8745d9becaa |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6bcc425588190afd0dceba43ed79f |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
| PDg | Predicate description generation | batch_69f6bbf5a8288190ae170bcbe8ab65cf |
completed | May 3, 2026, 3:07 a.m. |
Created at: April 29, 2026, 8:08 p.m.