Triple
T17050846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Speyside |
E413688
|
entity |
| Predicate | hasApproximateNumberOfDistilleries |
P125666
|
FINISHED |
| Object | over 40 |
—
|
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: over 40 | Statement: [Speyside, hasApproximateNumberOfDistilleries, over 40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateNumberOfDistilleries Context triple: [Speyside, hasApproximateNumberOfDistilleries, over 40]
-
A.
hasDistillery
Indicates that one entity owns, operates, or is associated with a distillery as a facility or production site.
-
B.
hasNearbyDistillery
Indicates that one entity is located close to or in the vicinity of a distillery.
-
C.
numberOfBreweries
Indicates the count of breweries associated with a given entity or within a specified context.
-
D.
hasNearbyDistilleryBrand
Indicates that one entity has a distillery brand located in close geographic proximity to it.
-
E.
distilleryType
Indicates the specific kind or category of distillery associated with an entity (e.g., craft, industrial, micro, or regional type).
- 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_69d886cde3d481908d4d01ba88ba7eb7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3daa26e84819098b41ae15618e813 |
completed | April 18, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69e35d60a588819084f53ef9f8b2e7c0 |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:34 a.m.