Triple

T6851081
Position Surface form Disambiguated ID Type / Status
Subject Grand Final parade E158014 entity
Predicate cityTradition P60104 FINISHED
Object Melbourne sporting culture 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: Melbourne sporting culture | Statement: [Grand Final parade, cityTradition, Melbourne sporting culture]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: cityTradition
Context triple: [Grand Final parade, cityTradition, Melbourne sporting culture]
  • A. establishedTradition
    Indicates that something has become a customary, long-standing practice or convention that is regularly followed within a group, culture, or context.
  • B. traditionSince
    Indicates that a tradition has been continuously practiced or recognized starting from a specified point in time.
  • C. traditionAt chosen
    Indicates that a particular tradition is practiced, observed, or associated at a specific place or location.
  • D. mainTradition
    Indicates that one entity represents the primary or dominant tradition associated with another entity.
  • E. culturalTradition
    Indicates a relationship where certain practices, beliefs, or customs are recognized as part of a shared cultural heritage passed down within a group or society.
  • 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_69c6882fae988190864cbba788c5ebb4 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d84c45708190918adfc028252400 completed March 27, 2026, 7:19 p.m.
PD Predicate disambiguation batch_69c6d0a12834819097d7e6c0b823745e completed March 27, 2026, 6:46 p.m.
Created at: March 27, 2026, 2:20 p.m.