Triple
T37855612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maize Rage (men's basketball) |
E944180
|
entity |
| Predicate | homeArenaSection |
P189554
|
FINISHED |
| Object | student section at Crisler Center |
—
|
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: student section at Crisler Center | Statement: [Maize Rage (men's basketball), homeArenaSection, student section at Crisler Center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeArenaSection Context triple: [Maize Rage (men's basketball), homeArenaSection, student section at Crisler Center]
-
A.
homeArenaFor
Indicates that a particular arena serves as the primary home venue for a specified sports team or organization.
-
B.
homeArenaUntil
Indicates that a particular venue served as an entity’s home arena up to a specified time or date.
-
C.
homeArenaSince
Indicates the point in time since which a particular arena has served as the designated home venue for a team or organization.
-
D.
homeArenaType
Indicates the type or category of arena that serves as the primary home venue for an entity.
-
E.
homeArenaState
Indicates the state or region in which a team's home arena is located.
- 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_69f76eed4d9c81908b1b71ba9e3b61fe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: May 3, 2026, 4:19 p.m.