Triple
T449776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Advance Australia Fair |
E7100
|
entity |
| Predicate | hasAlternativeVersions |
P455
|
FINISHED |
| Object | Indigenous language renditions |
—
|
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: Indigenous language renditions | Statement: [Advance Australia Fair, hasAlternativeVersions, Indigenous language renditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeVersions Context triple: [Advance Australia Fair, hasAlternativeVersions, Indigenous language renditions]
-
A.
isAlternativeTo
Indicates that one entity can serve as a substitute or different option in place of another.
-
B.
hasCoverVersions
Indicates that a musical work has one or more recorded versions performed or produced by artists other than the original creator.
-
C.
hasVariant
chosen
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
D.
hasInternationalVersion
Indicates that an entity has a corresponding version or counterpart adapted for use in multiple countries or international contexts.
-
E.
hasAlternativeZoneInCountry
Indicates that an entity has an alternative zone or area located within the specified country.
- 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_69a2e7e4676c81909ea0dbdecac0687c |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef691cc8819091729eaac52c9457 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2ede1a1108190a4a06b3416ae6156 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.