Triple
T2535039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michigan–Michigan State football rivalry |
E56247
|
entity |
| Predicate | fanBaseRegions |
P38712
|
FINISHED |
| Object | entire state of Michigan |
—
|
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: entire state of Michigan | Statement: [Michigan–Michigan State football rivalry, fanBaseRegions, entire state of Michigan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanBaseRegions Context triple: [Michigan–Michigan State football rivalry, fanBaseRegions, entire state of Michigan]
-
A.
fanBaseLocation
chosen
Indicates the primary geographic area where an individual’s or group’s supporters or fans are predominantly located.
-
B.
fanBase
Indicates that one entity is the group of admirers or supporters devoted to another entity.
-
C.
fanBaseScope
Indicates the extent or range of people who are considered fans or followers of an entity.
-
D.
participantsRegion
Indicates that the related entities are associated with, originate from, or operate within a specified geographic region.
-
E.
primaryRegionOfPopularity
Indicates the geographic region where something is most widely used, favored, or popular compared to other regions.
- 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_69ab4a49b6508190bc467fbef4bac334 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd64a2194819097c66cbeb37fe859 |
completed | March 7, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_69abd0c4a5dc819097812db50443420a |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:47 p.m.