Triple
T423187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schaefer Stadium |
E8148
|
entity |
| Predicate | alsoHosted |
P13575
|
FINISHED |
| Object | college football games |
—
|
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: college football games | Statement: [Schaefer Stadium, alsoHosted, college football games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoHosted Context triple: [Schaefer Stadium, alsoHosted, college football games]
-
A.
hosted
Indicates that one entity organized and provided the venue or platform for an event, activity, or presence involving another entity.
-
B.
coHostOf
Indicates a relationship where two or more entities jointly host the same event, program, or activity together.
-
C.
host
Indicates that one entity provides space, resources, or services to accommodate, receive, or entertain another entity.
-
D.
alsoServesAs
Indicates that one entity has an additional role, function, or identity that it fulfills simultaneously with its primary one.
-
E.
hostsCompany
Indicates that one entity provides space, infrastructure, or support for a company to operate, be located, or hold activities.
- F. None of above. chosen
Provenance (4 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eec200648190bcb9f1b98c8e9cdf |
completed | Feb. 28, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69a2edd5439c8190aea661b8b4aa51e9 |
completed | Feb. 28, 2026, 1:29 p.m. |
| PDg | Predicate description generation | batch_69a2ee8b56d08190bd625626353d01b4 |
completed | Feb. 28, 2026, 1:32 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.