Triple
T34224141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Captain Morgan |
E878000
|
entity |
| Predicate | consumptionLegalAgeRequirement |
P13636
|
FINISHED |
| Object | legal drinking age in jurisdiction |
—
|
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: legal drinking age in jurisdiction | Statement: [Captain Morgan, consumptionLegalAgeRequirement, legal drinking age in jurisdiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consumptionLegalAgeRequirement Context triple: [Captain Morgan, consumptionLegalAgeRequirement, legal drinking age in jurisdiction]
-
A.
legalAgeToPurchase
Indicates that an entity has reached the minimum legally permitted age to purchase a specified item or service.
-
B.
drinksLegalAge
chosen
Indicates that an entity has reached the minimum legal age required to consume alcoholic beverages.
-
C.
isAgeRestricted
Indicates that access to or use of something is limited based on the age of the person involved.
-
D.
ageLimitAppliesAt
Indicates the specific age or point in time at which an age-related restriction or limit becomes effective for an entity.
-
E.
ageLimitYears
Indicates the maximum allowed age, expressed in years, for which something is valid, permitted, or applicable.
- 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_69f349b16d0481908754e3069f05e0c1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:55 a.m.