Triple
T21434910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lagoa DOC |
E528781
|
entity |
| Predicate | hasParentAppellationSystem |
P37565
|
FINISHED |
| Object | Portuguese wine classification system |
—
|
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: Portuguese wine classification system | Statement: [Lagoa DOC, hasParentAppellationSystem, Portuguese wine classification system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentAppellationSystem Context triple: [Lagoa DOC, hasParentAppellationSystem, Portuguese wine classification system]
-
A.
hasSubAppellation
Indicates that one appellation (name or title) is a more specific or subordinate form of another appellation.
-
B.
hasParentSystem
chosen
Indicates that one system is hierarchically contained within or derived from another, which serves as its parent system.
-
C.
hasAppellationType
Indicates that an entity’s name or title is associated with a specific category or type of appellation.
-
D.
hasParentUnit
Indicates that one unit is hierarchically contained within or belongs to another, higher-level unit.
-
E.
hasParentSocietyType
Indicates that an entity is associated with, or belongs to, a broader parent society categorized by a specific type.
- 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_69e0c4569fa081908101baa24f8745db |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b536274c8190809bd3cdf4ef899e |
completed | April 22, 2026, 11:47 a.m. |
| PD | Predicate disambiguation | batch_69e61639ee288190889ffd500d1260f6 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 6 p.m.