Triple
T35300374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Friese Derby |
E1019486
|
entity |
| Predicate | cityOfOtherClub |
P30008
|
FINISHED |
| Object | Leeuwarden |
—
|
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: Leeuwarden | Statement: [Friese Derby, cityOfOtherClub, Leeuwarden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityOfOtherClub Context triple: [Friese Derby, cityOfOtherClub, Leeuwarden]
-
A.
hasFormerClub
Indicates that an entity (typically a person, such as an athlete) previously belonged to or was a member of a particular club or organization.
-
B.
parentClubCity
chosen
Indicates that a sports club is based in or belongs to a particular city as its home location.
-
C.
laterRepresentedClub
Indicates that an individual went on to represent a particular club at a later time than the contextually referenced period or affiliation.
-
D.
homeCityOfClubSupported
Indicates that a particular city is the home city of the sports club that an entity supports.
-
E.
usedByClubFromCity
Indicates that something (such as a facility, stadium, or resource) is utilized by a sports club that is based in a particular city.
- F. None of above.
Provenance (3 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:03 p.m.