Triple
T18675812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KV Mechelen |
E456597
|
entity |
| Predicate | hasRival |
P1375
|
FINISHED |
| Object | Beerschot AC |
—
|
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: Beerschot AC | Statement: [KV Mechelen, hasRival, Beerschot AC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Beerschot AC Context triple: [KV Mechelen, hasRival, Beerschot AC]
-
A.
Beerschot A.C.
chosen
Beerschot A.C. was a historic Belgian football club from Antwerp, known for its passionate fanbase and intense local derby rivalry with Royal Antwerp F.C.
-
B.
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.
-
C.
Zulte
Zulte is a municipality in the Belgian province of East Flanders.
-
D.
K Rupel Boom FC
K Rupel Boom FC is a Belgian football club based in the town of Boom, known for competing in the lower national divisions.
-
E.
K.S.C. Lokeren Oost-Vlaanderen
K.S.C. Lokeren Oost-Vlaanderen was a Belgian professional football club based in Lokeren, known for competing in the country’s top division and featuring several notable international players.
- 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_69d8d38f72b4819090a935175d9ca8af |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e556b5a52c81908a71ac86544fb6aa |
completed | April 19, 2026, 10:27 p.m. |
Created at: April 10, 2026, 11:48 a.m.