Triple
T22564223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FC Assen |
E557899
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | F.C. Assen |
—
|
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: F.C. Assen | Statement: [FC Assen, hasAbbreviation, F.C. Assen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: F.C. Assen Context triple: [FC Assen, hasAbbreviation, F.C. Assen]
-
A.
FC Assen
chosen
FC Assen is a Dutch football club based in the city of Assen in the Netherlands.
-
B.
RKC Waalwijk
RKC Waalwijk is a Dutch professional football club that competes in the national league system and is based in the town of Waalwijk in the Netherlands.
-
C.
SV Apeldoorn
SV Apeldoorn is a Dutch sports club based in the city of Apeldoorn, primarily known for its football activities.
-
D.
FC Eindhoven
FC Eindhoven is a Dutch professional football club from Eindhoven that competes in the country’s league system and shares a historic city rivalry with PSV Eindhoven.
-
E.
FC Emmen
FC Emmen is a professional Dutch football club based in the town of Emmen, known for competing in the country's top two league divisions.
- 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_69e11e5ae4ac8190b1f503457603d969 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15fa8d8388190856198547d56dce6 |
completed | April 29, 2026, 1:32 a.m. |
Created at: April 16, 2026, 8:52 p.m.