Triple
T12096390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epic 4-Day Pass |
E288080
|
entity |
| Predicate | usageLimit |
P98726
|
FINISHED |
| Object | maximum 4 days of lift access |
—
|
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: maximum 4 days of lift access | Statement: [Epic 4-Day Pass, usageLimit, maximum 4 days of lift access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usageLimit Context triple: [Epic 4-Day Pass, usageLimit, maximum 4 days of lift access]
-
A.
maximumUsage
chosen
Indicates the highest allowable or observed amount, frequency, or extent to which something can be used within a defined context or period.
-
B.
volumeLimitationBasis
Indicates the rule, criterion, or reference measure used as the basis for determining a limitation on volume.
-
C.
dailyQuota
Indicates the maximum amount or limit allocated or allowed for an entity within a single day.
-
D.
definesLimitOf
Indicates that one entity specifies or establishes the maximum or boundary condition applicable to another entity.
-
E.
gLimit
Indicates a constraint or maximum boundary imposed on the magnitude, rate, or extent of something within a given context.
- 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_69d6ab4964708190850585628b287b0c |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9178ad99c8190a54777b9bbe998bc |
completed | April 10, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69d915000454819089fee00022055599 |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:48 p.m.