Triple

T22248332
Position Surface form Disambiguated ID Type / Status
Subject CD Mérida E549904 entity
Predicate hasHistoricalLeagueLevel P91391 FINISHED
Object second tier of Spanish football 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: second tier of Spanish football | Statement: [CD Mérida, hasHistoricalLeagueLevel, second tier of Spanish football]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHistoricalLeagueLevel
Context triple: [CD Mérida, hasHistoricalLeagueLevel, second tier of Spanish football]
  • A. hasNonLeagueFootballHistory
    Indicates that an entity has a history of participation in football competitions outside the official league system.
  • B. hasExperienceInLeague
    Indicates that an entity has previously participated or been involved in a particular league.
  • C. hasHistoricFranchise
    Indicates that an entity is associated with or possesses a franchise that has historical significance or longstanding legacy.
  • D. hasLevelHistory
    Indicates that an entity is associated with a record or sequence of its past levels or states over time.
  • E. historicLeagueStatus chosen
    Indicates that an entity’s league affiliation or classification applied in the past (historically), rather than reflecting its current league status.
  • 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_69e11e41d9408190bd770cf282e22753 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f13219dc3481908dd987c4e98623e6 completed April 28, 2026, 10:18 p.m.
PD Predicate disambiguation batch_69e72fe1e0cc8190bd13cff2a0846225 completed April 21, 2026, 8:05 a.m.
Created at: April 16, 2026, 8:38 p.m.