Triple
T30569699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iowa Fight Song |
E778091
|
entity |
| Predicate | primaryFightSongOf |
P4835
|
FINISHED |
| Object | University of Iowa |
E58978
|
NE 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: University of Iowa | Statement: [Iowa Fight Song, primaryFightSongOf, University of Iowa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryFightSongOf Context triple: [Iowa Fight Song, primaryFightSongOf, University of Iowa]
-
A.
officialFightSong
chosen
Indicates that a particular song is formally designated as the official fight song of a team, school, or organization.
-
B.
battlecry
Indicates a relationship where an entity utters or uses a shouted phrase or chant to inspire, rally, or signal others, typically in preparation for or during conflict.
-
C.
battlecryChoice
Indicates the specific battle cry that an entity selects or uses, typically as a vocal expression before or during combat.
-
D.
isAnthemFor
Indicates that a song or musical composition serves as the official anthem representing a particular group, organization, place, or cause.
-
E.
diesFighting
Indicates that an entity dies as a direct result of engaging in a fight or combat.
- F. None of above.
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_69f2249f8c148190ae7eb3912cde112a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a02fcbe03d0819082d3dd715ed41623 |
completed | May 12, 2026, 10:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2870da88a881908b65ddd95e39645f |
completed | June 9, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_6a02fc62138081908d2dbc5db7541d13 |
completed | May 12, 2026, 10:09 a.m. |
Created at: April 29, 2026, 8:21 p.m.