Triple

T2846310
Position Surface form Disambiguated ID Type / Status
Subject Altay S.K. E62991 entity
Predicate isHistoricClub P4238 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: [Altay S.K., isHistoricClub, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isHistoricClub
Context triple: [Altay S.K., isHistoricClub, true]
  • A. isHistoric chosen
    Indicates that something has significant importance or relevance in history, often due to its age, impact, or role in past events.
  • B. hasHistoricFranchise
    Indicates that an entity is associated with or possesses a franchise that has historical significance or longstanding legacy.
  • C. isOldestClubIn
    Indicates that a club is the most ancient or earliest-established club within a specified place or organization.
  • D. hasClub
    Indicates that an entity is associated with or belongs to a particular club.
  • E. hasHistoricalEntity
    Indicates a relationship where one entity includes, references, or is associated with another entity that existed or is defined in a past historical 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_69ab4c407c408190857d25e027155ce9 completed March 6, 2026, 9:50 p.m.
NER Named-entity recognition batch_69abdf3d00708190966a477fdd855f23 completed March 7, 2026, 8:18 a.m.
PD Predicate disambiguation batch_69abdd0e86808190bcefffafbd3cd441 completed March 7, 2026, 8:08 a.m.
Created at: March 6, 2026, 10:02 p.m.