Triple
T18931208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weert |
E463111
|
entity |
| Predicate | hasSportsClub |
P346
|
FINISHED |
| Object | RKSV Weert |
—
|
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: RKSV Weert | Statement: [Weert, hasSportsClub, RKSV Weert]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RKSV Weert Context triple: [Weert, hasSportsClub, RKSV Weert]
-
A.
Weert
chosen
Weert is a municipality and city in the southeastern Netherlands known as a regional center in the province of Limburg.
-
B.
Knooppunt Rijnsweerd
Knooppunt Rijnsweerd is a major motorway interchange near Utrecht in the Netherlands, connecting several key highways and facilitating regional and national traffic flow.
-
C.
Westvoorne
Westvoorne is a coastal municipality in the Dutch province of South Holland, known for its beaches, dunes, and nature reserves.
-
D.
Oosterwijtwerd
Oosterwijtwerd is a small village in the province of Groningen in the northern Netherlands, known for its rural character and historic church.
-
E.
Buitenhof
Buitenhof is a residential neighborhood located in the Dutch municipality of Leiderdorp in South Holland.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c9c0b84881909ad6da9522203df8 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 10, 2026, 11:59 a.m.