Triple
T29937904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varnsdorf |
E760417
|
entity |
| Predicate | FK VarnsdorfPlaysIn |
P168277
|
FINISHED |
| Object | Czech National Football League |
—
|
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: Czech National Football League | Statement: [Varnsdorf, FK VarnsdorfPlaysIn, Czech National Football League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FK VarnsdorfPlaysIn Context triple: [Varnsdorf, FK VarnsdorfPlaysIn, Czech National Football League]
-
A.
clubNumberAt1FFCFrankfurt
Indicates the jersey number a player wears or wore while playing for 1. FFC Frankfurt.
-
B.
DDR-OberligaTitles
Indicates the number of DDR-Oberliga (East German top-division football league) titles an entity has won.
-
C.
foundedFootballClub
Indicates that a person or entity established or created a particular football club.
-
D.
nearFootballClub
Indicates that one entity is located close to, or in the immediate vicinity of, a football club.
-
E.
foundingClub
Indicates that one entity is a club that participated as a founding member in the creation or establishment of another entity (such as a league, organization, or competition).
- F. None of above. chosen
Provenance (4 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f677d6a2e08190a5769f96950b5e21 |
completed | May 2, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:21 p.m.