Triple
T38482750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Go Blue |
E917826
|
entity |
| Predicate | chantedIn |
P38181
|
FINISHED |
| Object | Michigan Stadium |
—
|
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: Michigan Stadium | Statement: [Go Blue, chantedIn, Michigan Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chantedIn Context triple: [Go Blue, chantedIn, Michigan Stadium]
-
A.
chanted
Indicates that an entity vocalized rhythmic or repetitive words or sounds, often in unison or with a steady cadence, directed toward another entity or in a particular context.
-
B.
chantedAt
Indicates that one entity directed chanting or rhythmic vocal expressions toward another entity as the target or audience.
-
C.
enchantedTo
Indicates that one entity has been magically imbued or altered so that it possesses a special effect, property, or behavior caused by another entity.
-
D.
alsoChantedIn
chosen
Indicates that a chant, hymn, or recitation is performed or used in an additional context, location, or tradition beyond its primary one.
-
E.
enchantedAs
Indicates that one entity has been placed under a magical spell or charm by another entity or force.
- 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_69f76e9894208190a129a553a60ca58c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.