Triple

T2604555
Position Surface form Disambiguated ID Type / Status
Subject Jewish Guild E58626 entity
Predicate featuredInternationalPlayers P13494 FINISHED
Object true 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: true | Statement: [Jewish Guild, featuredInternationalPlayers, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: featuredInternationalPlayers
Context triple: [Jewish Guild, featuredInternationalPlayers, true]
  • A. representedInternationallyBy
    Indicates that one entity serves as the official international representative or agent acting on behalf of another entity in foreign or global contexts.
  • B. featuresPlayersFrom chosen
    Indicates that something (such as a work, event, or production) includes or showcases players originating from a specified source, group, or location.
  • C. featuresTopPlayersFrom
    Indicates that something includes or showcases the most prominent or best-performing players from a specified source or group.
  • D. featuresTopPlayers
    Indicates that something prominently presents or showcases the most outstanding or highly ranked players.
  • E. keyInternationalOpponent
    Indicates that one entity is a primary or significant adversary or rival of another in an international context.
  • 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_69ab4ac3523881909679750c9f8c2dec completed March 6, 2026, 9:44 p.m.
NER Named-entity recognition batch_69abd8def9bc8190b2e013abffc7b191 completed March 7, 2026, 7:50 a.m.
PD Predicate disambiguation batch_69abd80ab7248190ba06ba14fe4c5638 completed March 7, 2026, 7:47 a.m.
Created at: March 6, 2026, 9:49 p.m.