Triple
T31113104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Die Roten Teufel |
E793007
|
entity |
| Predicate | associatedCityOfReferencedClub |
P83594
|
FINISHED |
| Object | Kaiserslautern |
E38581
|
NE FINISHED |
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: Kaiserslautern | Statement: [Die Roten Teufel, associatedCityOfReferencedClub, Kaiserslautern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCityOfReferencedClub Context triple: [Die Roten Teufel, associatedCityOfReferencedClub, Kaiserslautern]
-
A.
refersToClubBasedAt
Indicates that one entity makes reference to or is associated with a club that is based at a specified location or organization.
-
B.
parentClubCity
Indicates that a sports club is based in or belongs to a particular city as its home location.
-
C.
participatingClubsFromCity
Indicates that the clubs involved in an event or activity originate from or are based in a specified city.
-
D.
nicknameForClubFromCity
chosen
Indicates that a given nickname is used to refer to a sports club that is based in a particular city.
-
E.
homeCityDerbiesWith
Indicates that two sports teams regularly compete in derby matches against each other while being based in the same city.
- F. None of above.
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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2eb11933e08190b5483c6673a36bd0 |
completed | June 14, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:04 p.m.