Triple

T34905536
Position Surface form Disambiguated ID Type / Status
Subject Wien Neêrlands Bloed E1006715 entity
Predicate replacedAsNationalAnthem P145915 FINISHED
Object 1932 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: 1932 | Statement: [Wien Neêrlands Bloed, replacedAsNationalAnthem, 1932]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: replacedAsNationalAnthem
Context triple: [Wien Neêrlands Bloed, replacedAsNationalAnthem, 1932]
  • A. replacedAsAnthemBy chosen
    Indicates that one anthem has been superseded and officially taken over in its role by another anthem.
  • B. reconfirmedAsNationalAnthemInYear
    Indicates that something already designated as a national anthem was officially confirmed again in that role in a specified year.
  • C. adoptedAsProvisionalAnthem
    Indicates that a song or musical piece has been officially selected to serve temporarily as an anthem, pending a final or permanent choice.
  • D. usedAsNationalAnthemUntil
    Indicates that something served in the role of a national anthem up to a specified end time or date.
  • E. adoptedAsRegionalAnthem
    Indicates that a song or musical piece has been officially chosen and designated as the anthem for a specific region.
  • 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_69f76dc1b4a081909b4c6e4d8ec0aa2d completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fddd373cdc8190be1b12e70e4deb1f completed May 8, 2026, 12:55 p.m.
PD Predicate disambiguation batch_69fddc6915a88190ad41e379aa3ede13 completed May 8, 2026, 12:51 p.m.
Created at: May 3, 2026, 4 p.m.