Triple
T29988469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack Cleveland Casino |
E761795
|
entity |
| Predicate | legalAgeRequirement |
P95456
|
FINISHED |
| Object | 21 |
—
|
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: 21 | Statement: [Jack Cleveland Casino, legalAgeRequirement, 21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalAgeRequirement Context triple: [Jack Cleveland Casino, legalAgeRequirement, 21]
-
A.
maximumAgeRequirement
Indicates that there is an upper age limit that an entity must not exceed in order for a condition, participation, or eligibility to apply.
-
B.
legalAgeToPurchase
Indicates that an entity has reached the minimum legally permitted age to purchase a specified item or service.
-
C.
minimumRegistrationAge
Indicates the lowest age at which an entity is allowed or eligible to register for something.
-
D.
governsAgeEligibility
Indicates that one entity sets or controls the age-related criteria determining another entity’s eligibility for something.
-
E.
ageConstraint
chosen
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_69f2246851148190b8e76206db94b105 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: April 29, 2026, 6:37 p.m.