Triple
T463688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Napa |
E7396
|
entity |
| Predicate | regionSpecialty |
P466
|
FINISHED |
| Object | premium wines |
—
|
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: premium wines | Statement: [Napa, regionSpecialty, premium wines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionSpecialty Context triple: [Napa, regionSpecialty, premium wines]
-
A.
hasSpecialty
chosen
Indicates that an entity possesses a particular area of expertise, focus, or professional specialization.
-
B.
regionType
Indicates the classification or category of a region, specifying what kind of region it is (e.g., administrative, geographic, or functional).
-
C.
regionSpecificContent
Indicates that certain content is tailored, restricted, or applicable only to a particular geographic region or set of regions.
-
D.
specialMunicipality
Indicates that an entity is designated as a special municipality, typically having a distinct administrative or legal status compared to regular municipalities.
-
E.
sectorServed
Indicates the industry or economic sector that an entity primarily serves or targets with its activities, products, or services.
- 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efc214788190a8dff20fec4412e0 |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2ede8eac081908dffade6a5e7950b |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.