Triple
T18340250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memorial Stadium (Clemson) |
E439382
|
entity |
| Predicate | openedForUseInSeason |
P106970
|
FINISHED |
| Object | 1942 college football 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: 1942 college football season | Statement: [Memorial Stadium (Clemson), openedForUseInSeason, 1942 college football season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForUseInSeason Context triple: [Memorial Stadium (Clemson), openedForUseInSeason, 1942 college football season]
-
A.
openingForSeason
chosen
Indicates the event or action of beginning a new operational or active season for something (such as a venue, activity, or service).
-
B.
openedForCurrentUse
Indicates that an entity has been opened and is currently available for its intended use or operation.
-
C.
openSeasonally
Indicates that an entity operates or is accessible only during specific seasons or times of the year.
-
D.
openedForUse
Indicates that something has been made accessible and available for its intended operation or use.
-
E.
openedForUseBy
Indicates that something has been made available or activated so that a particular entity can use it.
- 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_69d8b9175fec8190af865699b4e64d8c |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50ed146fc819092b08cb91defb03b |
completed | April 19, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69e44fe91bc08190906518e1b120fcf0 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:37 a.m.