Triple
T12010335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epic College Pass |
E285887
|
entity |
| Predicate | validDuring |
P9768
|
FINISHED |
| Object | winter ski season |
—
|
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: winter ski season | Statement: [Epic College Pass, validDuring, winter ski season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: validDuring Context triple: [Epic College Pass, validDuring, winter ski season]
-
A.
validIn
chosen
Indicates that a given entity, statement, or condition is applicable, correct, or legally/semantically acceptable within a specified context, scope, or domain.
-
B.
wasInForceDuring
Indicates that a rule, law, agreement, or other normative provision was legally valid and operative throughout a specified time period.
-
C.
usedDuring
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
-
D.
validatedAt
Indicates the specific time at which something was checked and confirmed as correct, acceptable, or officially approved.
-
E.
rulesDuring
Indicates that one entity holds authority or governance over another throughout a specified time period or interval.
- 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903d7777481908cd5a001f75e2ee3 |
completed | April 10, 2026, 2:06 p.m. |
| PD | Predicate disambiguation | batch_69d902b245cc8190af96a9c2bd9c6250 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.