Triple
T15113385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Pavilion at Ole Miss |
E360970
|
entity |
| Predicate | openedWithEvent |
P16243
|
FINISHED |
| Object | Ole Miss vs. Alabama men's basketball game |
—
|
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: Ole Miss vs. Alabama men's basketball game | Statement: [The Pavilion at Ole Miss, openedWithEvent, Ole Miss vs. Alabama men's basketball game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedWithEvent Context triple: [The Pavilion at Ole Miss, openedWithEvent, Ole Miss vs. Alabama men's basketball game]
-
A.
openedWith
Indicates that an entity is opened, initiated, or accessed using a specified tool, method, or instrument.
-
B.
openedForEvent
chosen
Indicates that a venue or location is made accessible and operational specifically for a particular event.
-
C.
openedAs
Indicates that one entity began operating, functioning, or being available to the public under the form, name, or role of another entity.
-
D.
openedIn
Indicates that an entity (such as a business, event, or institution) began operating or was inaugurated in a specific time period or location.
-
E.
openedAfter
Indicates that one entity was opened at a later time than another entity.
- 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0058d786c8190937c6819255c01bd |
completed | April 15, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69deb96c1d9c81909351558ed97bc5b7 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:05 a.m.