Triple
T22800956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Pulteney Distillery |
E564388
|
entity |
| Predicate | ageStatementRange |
P2736
|
FINISHED |
| Object | non-age-statement to 18 years and above |
—
|
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: non-age-statement to 18 years and above | Statement: [Old Pulteney Distillery, ageStatementRange, non-age-statement to 18 years and above]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageStatementRange Context triple: [Old Pulteney Distillery, ageStatementRange, non-age-statement to 18 years and above]
-
A.
ageStatement
Indicates that a statement expresses or asserts the age of an entity in terms of time lived or existed.
-
B.
ageRange
chosen
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
C.
ageRangeUpper
Indicates the maximum age limit that bounds the upper end of an age range associated with an entity or relationship.
-
D.
hasApproximateAgeRange
Indicates that one entity is associated with another entity representing an estimated or non-exact span of ages.
-
E.
ageConstraint
Indicates a restriction or condition based on the age of an entity relative to a specified threshold or range.
- 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_69e2458185f88190b0045227ee420411 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17cdd87648190ba30f0b8f3ef7346 |
completed | April 29, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:31 p.m.