Triple

T21414565
Position Surface form Disambiguated ID Type / Status
Subject R.S.C. Anderlecht E528266 entity
Predicate basedIn P40 FINISHED
Object Anderlecht NE NERFINISHED

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: Anderlecht | Statement: [R.S.C. Anderlecht, basedIn, Anderlecht]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Anderlecht
Context triple: [R.S.C. Anderlecht, basedIn, Anderlecht]
  • A. Anderlecht chosen
    Anderlecht is a municipality in the Brussels-Capital Region of Belgium, known for its historic center and prominent football club R.S.C. Anderlecht.
  • B. R.S.C. Anderlecht
    R.S.C. Anderlecht is a Belgian professional football club from Brussels, renowned as one of the country’s most successful and decorated teams.
  • C. Royal Antwerp F.C.
    Royal Antwerp F.C. is a historic Belgian professional football club based in Antwerp and one of the oldest clubs in the country.
  • D. Waasland-Beveren
    Waasland-Beveren is a Belgian professional football club based in Beveren, known for competing in the country’s football league system.
  • E. Royal Charleroi Sporting Club
    Royal Charleroi Sporting Club is a professional Belgian football club based in Charleroi that competes in the country’s top-tier league.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c454c248819093425d1099101c09 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69e8b2032fe48190907b282e2fffa2bd completed April 22, 2026, 11:33 a.m.
Created at: April 16, 2026, 5:45 p.m.