Triple
T6613483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madeira wine |
E149290
|
entity |
| Predicate | hasQualityCategory |
P33477
|
FINISHED |
| Object | Finest |
—
|
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: Finest | Statement: [Madeira wine, hasQualityCategory, Finest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQualityCategory Context triple: [Madeira wine, hasQualityCategory, Finest]
-
A.
hasQualityCriterion
Indicates that something is associated with a specific standard or criterion used to judge its quality.
-
B.
hasCategoryOn
Indicates that something is assigned to or associated with a specific category within a given context or scope.
-
C.
hasSpecialCategory
Indicates that an entity is associated with a designated special or exceptional category distinct from its standard classifications.
-
D.
hasQualifier
Indicates that one entity serves as a qualifier or modifier that further specifies or restricts the meaning or scope of another entity or statement.
-
E.
hasCategoryLevel
chosen
Indicates that something is associated with a specific hierarchical category or tier within a classification system.
- 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_69c687ebc680819094caf71faba2efe2 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cf3796d08190a26e988386089447 |
completed | March 27, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69c6acfed25481909cac74c84a9fe088 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:57 p.m.