Triple
T15219868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schaerbeek |
E363736
|
entity |
| Predicate | hasNeighbour |
P5707
|
FINISHED |
| Object | Anderlecht |
E528266
|
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: Anderlecht | Statement: [Schaerbeek, hasNeighbour, Anderlecht]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Anderlecht Context triple: [Schaerbeek, hasNeighbour, 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 Football Club de Liège
Royal Football Club de Liège is a historic Belgian football club from the city of Liège, known as one of the country’s oldest and most traditional teams.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007709d3881908384f0fe1e0218d0 |
completed | April 15, 2026, 9:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fed345d58c81908a8fd182c0fe7c15 |
completed | May 9, 2026, 6:25 a.m. |
Created at: April 10, 2026, 3:11 a.m.