Triple

T13551409
Position Surface form Disambiguated ID Type / Status
Subject Polish SuperCup E323652 entity
Predicate relatedDomesticCounterpart P6587 FINISHED
Object Polish Cup final 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: Polish Cup final | Statement: [Polish SuperCup, relatedDomesticCounterpart, Polish Cup final]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relatedDomesticCounterpart
Context triple: [Polish SuperCup, relatedDomesticCounterpart, Polish Cup final]
  • A. relatedCountry
    Indicates that there is a relevant or associated relationship between an entity and a specified country, without specifying the exact nature of that relationship.
  • B. isLinkedEconomicallyTo
    Indicates that two entities are connected through economic relationships such as trade, investment, financial flows, or shared market dependencies.
  • C. hasCounterpart chosen
    Indicates that one entity corresponds to, matches, or serves as an equivalent or parallel version of another entity.
  • D. counterpartRelation
    Indicates a reciprocal relationship where two entities serve as corresponding or equivalent counterparts to each other in a given context.
  • E. relatedExchange
    Indicates that there is a connection or association between two exchanges or exchange-related events.
  • 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_69d8076776248190bdf0d4fa1f85a5fc completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbbb9ee3f081909056dc1a92c40b7a completed April 12, 2026, 3:34 p.m.
PD Predicate disambiguation batch_69dbae13bec4819084c1770638c00ed9 completed April 12, 2026, 2:37 p.m.
Created at: April 9, 2026, 9:46 p.m.