Triple
T24469540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michigan–Michigan State men's ice hockey rivalry |
E617060
|
entity |
| Predicate | campusCityTeam2 |
P156220
|
FINISHED |
| Object | East Lansing, Michigan |
—
|
NE NERFINISHED |
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: East Lansing, Michigan | Statement: [Michigan–Michigan State men's ice hockey rivalry, campusCityTeam2, East Lansing, Michigan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campusCityTeam2 Context triple: [Michigan–Michigan State men's ice hockey rivalry, campusCityTeam2, East Lansing, Michigan]
-
A.
campusOfTeam
Indicates the campus or primary location associated with a particular team.
-
B.
campus2
Indicates that one entity is a secondary or additional campus location associated with another primary campus or institution.
-
C.
campus1
Indicates a relationship where an entity is identified as a campus or is located on/associated with a particular campus.
-
D.
cityTeam2
Indicates that a team is based in, represents, or is associated with a particular city.
-
E.
cityCampus
Indicates that a campus is located within or associated with a particular city.
- 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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f299422cdc8190bc8d56243b7bc313 |
completed | April 29, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:20 a.m.