Triple
T31113105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Die Roten Teufel |
E793007
|
entity |
| Predicate | associatedStateOfReferencedClub |
P83595
|
FINISHED |
| Object | Rhineland-Palatinate |
E101388
|
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: Rhineland-Palatinate | Statement: [Die Roten Teufel, associatedStateOfReferencedClub, Rhineland-Palatinate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedStateOfReferencedClub Context triple: [Die Roten Teufel, associatedStateOfReferencedClub, Rhineland-Palatinate]
-
A.
associatedClubState
chosen
Indicates that there is a relationship between an entity and the state-level club or organization with which it is formally connected or affiliated.
-
B.
associatedClubPredecessorState
Indicates that a club is linked to a predecessor entity that existed in an earlier state or form of the organization.
-
C.
affiliatedClubOf
Indicates that one entity is a club with which another entity is formally associated or connected.
-
D.
associatedClubStatus
Indicates the status or condition of a club as it relates to a particular entity or relationship.
-
E.
associatedClub2
Indicates that an entity has a secondary or additional affiliation or membership with a particular club.
- 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_6a2947135cec8190897ffaea6cff3a6b |
completed | June 10, 2026, 11:14 a.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:04 p.m.