Triple
T21132117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uden |
E520711
|
entity |
| Predicate | hasSportsClub |
P346
|
FINISHED |
| Object | FC Uden |
—
|
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: FC Uden | Statement: [Uden, hasSportsClub, FC Uden]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FC Uden Context triple: [Uden, hasSportsClub, FC Uden]
-
A.
FC Uden
chosen
FC Uden is a local football club based in the town of Uden in the Netherlands.
-
B.
FC Utrecht
FC Utrecht is a professional Dutch football club based in Utrecht that competes in the Eredivisie and is regarded as one of the country’s prominent teams.
-
C.
FC Volendam
FC Volendam is a Dutch professional football club based in Volendam, known for its distinctive orange kits and history of developing talented players.
-
D.
FC Wil
FC Wil is a Swiss professional football club based in Wil, known for competing in the Swiss leagues and maintaining a regional rivalry with FC St. Gallen.
-
E.
FC Den Bosch
FC Den Bosch is a professional Dutch football club based in 's-Hertogenbosch that competes in the country's league system, traditionally in the Eerste Divisie.
- 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_69e0b50b53048190ae34e8abbe3c5ada |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e723574b1481909fe9bebc83f1f3ce |
completed | April 21, 2026, 7:12 a.m. |
Created at: April 16, 2026, 2:56 p.m.