Triple
T31113131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waldhof Mannheim |
E793008
|
entity |
| Predicate | hasRivalriesType |
P146762
|
FINISHED |
| Object | historic regional rivalries |
—
|
LITERAL 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: historic regional rivalries | Statement: [Waldhof Mannheim, hasRivalriesType, historic regional rivalries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRivalriesType Context triple: [Waldhof Mannheim, hasRivalriesType, historic regional rivalries]
-
A.
hasRivalryCategory
chosen
Indicates that there exists a competitive or adversarial relationship between entities that falls into a specific classified type or category of rivalry.
-
B.
hasInStateRivalries
Indicates that two entities are rivals or competitors within the same state or internal jurisdiction.
-
C.
hasRivalryAspect
Indicates that there exists a competitive or adversarial relationship or dimension between entities.
-
D.
hasRivalryContext
Indicates that there exists a competitive or adversarial relationship between entities within a specific situational or contextual framework.
-
E.
hasRivalryFormat
Indicates that there is a specific structure, set of rules, or format that defines how a rivalry between entities is conducted or organized.
- 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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 29, 2026, 9:04 p.m.