Triple

T33546255
Position Surface form Disambiguated ID Type / Status
Subject Stade Municipal de Berkane E859214 entity
Predicate homeStadiumOf P2696 FINISHED
Object RS Berkane
RS Berkane is a Moroccan professional football club based in Berkane that competes in the country’s top division and has gained prominence in African club competitions.
E2055466 NE 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: RS Berkane | Statement: [Stade Municipal de Berkane, homeStadiumOf, RS Berkane]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: RS Berkane
Triple: [Stade Municipal de Berkane, homeStadiumOf, RS Berkane]
Generated description
RS Berkane is a Moroccan professional football club based in Berkane that competes in the country’s top division and has gained prominence in African club competitions.

Provenance (5 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_69f3497a5be08190a39b12736899e034 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6f6e6c7548190a04def6ce41f0bc0 completed May 3, 2026, 7:19 a.m.
NED1 Entity disambiguation (via context triple) batch_6a35a68ab5f48190b571f6c49573bf3c completed June 19, 2026, 8:28 p.m.
NEDg Description generation batch_6a35a71051648190a33ed02afc5c6798 completed June 19, 2026, 8:31 p.m.
NED2 Entity disambiguation (via description) batch_6a35a7e144548190908e3e6ddf96362a completed June 19, 2026, 8:34 p.m.
Created at: May 1, 2026, 1:39 a.m.