Triple

T10294933
Position Surface form Disambiguated ID Type / Status
Subject Clásico del Astillero E241458 entity
Predicate derbyStatus P39572 FINISHED
Object flagship derby of Ecuadorian 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: flagship derby of Ecuadorian football | Statement: [Clásico del Astillero, derbyStatus, flagship derby of Ecuadorian football]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: derbyStatus
Context triple: [Clásico del Astillero, derbyStatus, flagship derby of Ecuadorian football]
  • A. derby
    Indicates a competitive match or contest, typically between closely linked or rival entities (such as teams from the same area or group).
  • B. hasDerbyStatus chosen
    Indicates that an entity holds a specific status or classification related to a derby event or competition.
  • C. derbyInvolves
    Indicates that a particular derby event includes or features the participation of a specified entity or entities.
  • D. derbyInLeagueSystem
    Indicates that a derby (a match between local rivals) takes place within, and is organized as part of, a specific league system.
  • E. regionDerby
    Indicates a competitive match or rivalry that takes place between teams or participants from the same geographic region.
  • 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_69d381aaafc08190af475ef58dc16aba completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4d2d5e0f88190be3e23ba2511a1e9 completed April 7, 2026, 9:48 a.m.
PD Predicate disambiguation batch_69d4d1f35e548190be3b4d92d65d2d20 completed April 7, 2026, 9:44 a.m.
Created at: April 6, 2026, 11:42 a.m.