Triple
T12215493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epic 7-Day Pass |
E291072
|
entity |
| Predicate | hasDurationInDays |
P64465
|
FINISHED |
| Object | 7 |
—
|
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: 7 | Statement: [Epic 7-Day Pass, hasDurationInDays, 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDurationInDays Context triple: [Epic 7-Day Pass, hasDurationInDays, 7]
-
A.
hasDays
Indicates that an entity is associated with, spans, or occurs on specific days.
-
B.
hasDurationType
Indicates that something is associated with a specific kind or category of duration (e.g., temporary, permanent, short-term, long-term).
-
C.
hasDayCount
chosen
Indicates that an entity is associated with a specific number of days, expressing the duration or count of days related to it.
-
D.
possibleLengthDays
Indicates that an entity can have a duration, measured in whole or fractional days, equal to the specified value.
-
E.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
- 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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d920e312708190b4aede2e21f5f697 |
completed | April 10, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69d91c3d669c81908eea7ad61122d275 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.