Triple
T442081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michigan Wolverines football |
E10133
|
entity |
| Predicate | hasWinningTradition |
P13220
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Michigan Wolverines football, hasWinningTradition, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWinningTradition Context triple: [Michigan Wolverines football, hasWinningTradition, true]
-
A.
traditionSince
Indicates that a tradition has been continuously practiced or recognized starting from a specified point in time.
-
B.
traditionallyOneOf
Indicates that something is customarily or historically considered to belong to a specific set, category, or group.
-
C.
historicallyPrizedFor
Indicates that something has been especially valued or esteemed for a particular quality, use, or significance in the past.
-
D.
hasTraditionalSymbol
Indicates that something is associated with or represented by a conventional or culturally established symbol.
-
E.
culturalTradition
Indicates a relationship where certain practices, beliefs, or customs are recognized as part of a shared cultural heritage passed down within a group or society.
- 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_69a2e8465ef481909655c681b01e2986 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2ef42b4008190abed9d79926c7022 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2edde2b9c8190bd20b582eb4c5065 |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eeb9e6b0819093863959a6e5730a |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.