Triple

T26906860
Position Surface form Disambiguated ID Type / Status
Subject Royal Antwerp F.C. E677276 entity
Predicate hasHistoricNicknameMeaning P155766 FINISHED
Object oldest club in Belgian football system 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: oldest club in Belgian football system | Statement: [Royal Antwerp F.C., hasHistoricNicknameMeaning, oldest club in Belgian football system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHistoricNicknameMeaning
Context triple: [Royal Antwerp F.C., hasHistoricNicknameMeaning, oldest club in Belgian football system]
  • A. hasHistoricNickname
    Indicates that an entity is known by a nickname that has historical significance or longstanding traditional use.
  • B. hasHistoricalMeaning chosen
    Indicates that something carries significance, symbolism, or relevance derived from past events, contexts, or traditions.
  • C. historicalOriginMeaning
    Indicates that one entity explains the original historical source or derivational meaning of another entity.
  • D. isHistoricalName
    Indicates that a given name is a former or past designation historically used for an entity.
  • E. historicalNameUsedIn
    Indicates that a historical or former name was used to refer to a particular entity in some 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_69eee9bcef1c8190be88586bb902bb9b completed April 27, 2026, 4:44 a.m.
NER Named-entity recognition batch_69f7b0e5744c8190a22c1e1d6fcfa466 completed May 3, 2026, 8:32 p.m.
PD Predicate disambiguation batch_69f7ab70d034819080295628497d8582 completed May 3, 2026, 8:09 p.m.
Created at: April 27, 2026, 5:59 a.m.