Triple

T25220452
Position Surface form Disambiguated ID Type / Status
Subject Show Court One E631946 entity
Predicate relativeImportanceAtVenue P89351 FINISHED
Object key tennis venue at Melbourne Park 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: key tennis venue at Melbourne Park | Statement: [Show Court One, relativeImportanceAtVenue, key tennis venue at Melbourne Park]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relativeImportanceAtVenue
Context triple: [Show Court One, relativeImportanceAtVenue, key tennis venue at Melbourne Park]
  • A. localImportance chosen
    Indicates that something holds particular significance, influence, or priority within a specific, limited context or area rather than globally.
  • B. relativeImportanceAtAirport
    Indicates the comparative level of importance or priority assigned to entities within the context of an airport.
  • C. relativeImportanceInCountry
    Indicates the comparative significance or priority of something within the context of a specific country.
  • D. importanceInEvent
    Indicates the degree to which an entity plays a significant or central role within a particular event.
  • E. relativeImportanceToTeam2
    Indicates the comparative level of importance or value that one entity has relative to another within the context of a team.
  • 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_69e75a8e0f688190a7aebe9a4815e25b completed April 21, 2026, 11:07 a.m.
NER Named-entity recognition batch_69f74062b9388190b30546cf700a825c completed May 3, 2026, 12:32 p.m.
PD Predicate disambiguation batch_69f73c802b848190b61a416b7488bd96 completed May 3, 2026, 12:16 p.m.
Created at: April 21, 2026, 1:03 p.m.