Triple
T3323520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maroons |
E69853
|
entity |
| Predicate | anthemOrSong |
P14687
|
FINISHED |
| Object | "Queenslander" chant |
—
|
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: "Queenslander" chant | Statement: [Maroons, anthemOrSong, "Queenslander" chant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: anthemOrSong Context triple: [Maroons, anthemOrSong, "Queenslander" chant]
-
A.
anthemType
Indicates the specific category or kind of anthem that characterizes the relationship between the subject and its anthem.
-
B.
isAnthemFor
Indicates that a song or musical composition serves as the official anthem representing a particular group, organization, place, or cause.
-
C.
anthemComposer
Indicates that one entity is the person who composed the anthem associated with another entity.
-
D.
anthemBackedBy
Indicates that an anthem is officially supported, endorsed, or accompanied by a particular backing entity, such as an organization, arrangement, or musical backing.
-
E.
officialSong
chosen
Indicates that a song has been formally designated as the official musical piece associated with a particular entity, such as an event, organization, or place.
- 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_69ad85a1829881908942c14075644d0d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb13e6c288190805f8abcd3acc906 |
completed | March 8, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69ada42a19348190a3862ce02451f4aa |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.